Thanks for the response,
Regarding...
> Don't get me wrong, [subselects are] neat to have,
> but I really don't mind waiting...
> Are there other factors?
Yeah, we have SQL "dynamically" generated from "SQL
Generator" code which is bombing out with queries
having > 32 table joins and this will
> 1) ACID compliant transaction support. There is
> concern as to whether InnoDB is ready for prime time,
> especially as regards backups and our 24X7 needs. Our
> databases can grow very rapidly and we can't afford to
> bounce the database just to add datafiles as is
> currently required for Inno
In light of recent vigorous discussion on SlashDot
concerning MySQL vs PostgreSQL vs SAPDB, etc... my
management is contemplating dropping MySQL support :-(
in favor of PostgreSQL or Firebird/Interbase and I
need some help/ammo from you guys to defend MySQL.
Here are the concerns:
1) ACID compli
