| From: | Philip Yarra <philip(at)utiba(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL not ACID compliant? |
| Date: | 2003-09-20 01:05:58 |
| Message-ID: | Pine.LNX.4.44.0309201053110.27892-100000@ser1.cpc.net.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
It's funny timing - I had to prepare a comparison between PostgreSQL and
MySQL recently, explaining why we would prefer PostgreSQL. I know some
people here have issues with the MySQL crashme test results, but I have to
say I found it possibly one of the best postgreSQL advertisements
available. A 4-way comparison between Sybase, Oracle, MySQL and PostgreSQL
shows PostgreSQL in an extremely flattering light.
Given the missing features in MySQL (column constraints and views, for
god's sake!) I had to
conclude that we couldn't implement most of our projects in MySQL, even if
we wanted to. I have trouble believing MySQL was suggested as a viable
alternative.
I know I'm preaching to the choir here, but thought you might find it of
interest.
Regards, Philip Yarra.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2003-09-20 01:11:09 | Re: PostgreSQL not ACID compliant? |
| Previous Message | Joshua D. Drake | 2003-09-20 00:48:26 | Re: PostgreSQL not ACID compliant? |