| From: | Tino Wildenhain <tino(at)wildenhain(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Vivek Khera <vivek(at)khera(dot)org>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: To Postgres or not |
| Date: | 2005-07-14 08:08:41 |
| Message-ID: | 1121328521.20011.21.camel@sabrina.peacock.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am Donnerstag, den 14.07.2005, 00:57 -0400 schrieb Alvaro Herrera:
> On Thu, Jul 14, 2005 at 02:46:01PM +1000, Neil Conway wrote:
> > Vivek Khera wrote:
> > >The first sentence rules out MySQL, so the second sentence should read
> > >"So that leaves Postgres". Your problem is solved ;-)
> > >
> > >(If you are accustomed to Oracle, you are probably expecting an ACID
> > >database, which rules out MySQL too).
> >
> > Does MySQL with InnoDB not qualify as an ACID-compliant database?
>
> Not if you intermix InnoDB tables with MyISAM tables, which AFAIK many
> people seem to do.
Even not in a clean InnoDB environment because still data is silently
truncated. (e.g. smallint takes 200 and truncates it to 127. Thats not
ACID :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Seltenreich | 2005-07-14 08:09:44 | Re: Case insensitive unique constraint |
| Previous Message | Klint Gore | 2005-07-14 08:06:41 | Re: Case insensitive unique constraint |