[Gllug] Why not to use MySQL...

[Rev Simon Rumble]

On Mon 24 Nov, Daniel P. Berrange bloviated thus:
> People are often asking whether to use PostgreSQL or MySQL for web
> applications. Well the performance argument is pretty irrelevant these 
> days, since PG has improved drammatically in the course of the 7.x 
> series & is easily comparable with MySQL. So it should comes down to 
> is their comparative levels of support for the SQL standards. Or in
> the MySQL case, all the horrific ways in which is deviates from the
> spec.

MySQL only ever won read-only benchmarks.  The moment you got some
real-world data and ended up locking an entire table for a write, and
had two simultaneous writes to the same table, it would go splat.

The main thing about MySQL is that the developers claimed you didn't
need to be ACID to be a database, and that transactions are
unnecessary.  Now that they've finally added transactions, you have to
wonder what changed to make them need it and what other shortcuts
they've taken in the name of performance and data loss.

> Let the flamewars commence.... :-)

Flame on!

-- 
Rev Simon Rumble <simon at rumble.net>
www.rumble.net

 "If a law is unjust, a man is not only right to disobey it,
  he is obligated to do so."
- Thomas Jefferson

-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug