Re: Need concrete "Why Postgres not MySQL" bullet list

In article <200308200839(dot)28230(dot)josh(at)agliodbs(dot)com>,
Josh Berkus <josh(at)agliodbs(dot)com> writes:

> PROCEDURES: Postgres supports stored procedures (as functions) allowing
> programming in the database for the many tasks which are far more efficient,
> consistent, and secure done there. Procedures may be written in any of nine
> different languages, currently, with two more in development. MySQL does not
> support procedures at all.

From the MySQL manual:
* With UDF (user-defined functions) one can extend MySQL Server with
both normal SQL functions and aggregates, but this is not yet as
easy or as flexible as in PostgreSQL.

> TRANSACTIONS: blah, blah, blah. MySQL has just begun offering transactions
> this year, and their solution is largely untested, slow...

InnoDB transactions in MySQL are pretty robust and fast. However,
this affects only INSERT/UPDATE/DELETE - not CREATE TABLE etc.

> and suffers from
> complications with the many different "table types".

True. Transactions break unless all tables used are InnoDB.