Robert,
> Honestly I would like to see gotchas type pages created for every database;
> if someone asks me why they should choose postgresql i have that covered,
> but if someone asks me why they might want to migrate from $ql server to
> postgresql, that would be a lot tougher since i don't have to regulary deal
> with it. As long as the information on these pages is well researched,
> correct, documented, and responsive to being changed, I don't think it's
> uncalled for.
But *all* this page is is backup to the statement "MySQL is not fully ACID
compliant and has weak SQL Standard compliance." If the requester wants
backup on that, THEN you show them the Gotchas page. But you DON'T send this
page to them in response to the initial question "Why should I choose MySQL
vs. PostgreSQL?". The Gotchas do NOT answer that question.
We do need the page to enforce any statements about differences in ACID
compliance between MySQL and PostgreSQL and should maintain it. But only if
someone asks.
For one thing, you're just challenging MySQL to come up with a similar page
for PostgreSQL. And they have a half dozen full-time marketing staff who
can devote their full energies to the task -- and gods know PostgreSQL has
its faults too.
A page listing the faults of MySQL on its own does not tell a member of the
public why they should choose PostgreSQL, it tells them why they should
choose Oracle.
--
Josh Berkus
Aglio Database Solutions
San Francisco