Re: To Postgres or not

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
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 14:53:33
Message-ID: 1121352813.8208.262.camel@state.g2switchworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2005-07-13 at 23:57, Alvaro Herrera wrote:
> 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.

And the tendency to NOT throw errors or warnings is frightening.

create table blah (field1 int, field2 text) type=inoodb

will gladly create a myisam table, no warnings, no errors, nothing
else. Then if you try to start a transaction on it, it quietly starts
it, no errors again, until you try to roll it back.

Sorry, but that does NOT qualify as ACID, no matter what some folks may
say on their blogs.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matt Miller 2005-07-14 15:38:43 Re: Standalone Parser for PL/pgSQL
Previous Message Tony Caduto 2005-07-14 14:50:54 Re: Quotation marks in queries