MySQL doesn't even support self referential updates like
update t1 set c1 ='value' where t1.id not in (select id from t1 where id >
100);
Nor is it fully ACID compliant.
And its online documentation is a nightmare.
PgAdmin is infintely better than mysql workbench, heck anything is better
than MySQLWorkbench
Postgres as of 9 will do pretty much anything Oracle or mssql will do minus
robust tools (where mssql is a clear winner with ssrs and ssis and ssms).
Oracles tools are coming around with developer, modeler, and analytics but
really oracle is for when you need serious distributed transaction balancing
via RAC. Honestly if your not using RAC there is no reason to use Oracle.
So There is not one reason to go with MySQL over Postgres and tons of reason
to use Postgres over MySQL, arrays, ORM, Tools, Documentation,
Cross-Language Support, Faster, ACID compliant, etc
And if you want a really rich toolset and you have bought into the .NET
library model, which once you start digging is quite cool, go read petzolds
DotNETZero, then go with mssql.
And if your running a transaction volume to rival Amazon and want a db that
can come as close to a true parrallel load balancing as RAC then fork aout
the shiny and go with Oracle.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Too-far-out-of-the-mainstream-tp5722177p5722878.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
