[plug] Web database stuff - Bollocks

[Hook]

Simon Scott wrote:
> Its quite simple
>
> MySQL is super quick, but lacks some features (like transactions and
> row locking)

Not so. Mysql offers a variety of table types, some of which offer
transactions and row locking. Tying it into the type of table is an
interesting approach, but I can imagine that you could get yourself into
real trouble unless you're careful !

> Postgresql is slower, but more 'high end' and supports row locking,
> transactions, and a host of other highend features.
>
> If you're writing a dynamic website, use MySQL. If youre writing a
> web-based application, use postgresql.

I'd be interested in knowing why you make the application split like this. I
have no postgresql experience, but the impression is that it's a true RDBMS,
which Mysql isn't (it has relational integrity for example), but that this
comes with a performance penalty. As I said, this is from reading and
listening rather than doing, so I'd be interested to hear different views.

> Either way, with PHP (which I recommend for small/medium projects),
> abstract the mysql and pgsql functions into a library so you can easily
> switch between the two as necessary. PHP doesnt give you a 'database
layer',
> it simply provides functions specific to each database. They leave the
> abstraction up to you.

True, a good approach, as is Perl and (for the brave and those with time to
spare) C.

The Hooker