Re: 'Official' definition of ACID compliance?

From: Jaime Casanova <systemguards(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-general(at)postgresql(dot)org, Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Russ Brown <pickscrape(at)gmail(dot)com>
Subject: Re: 'Official' definition of ACID compliance?
Date: 2006-01-05 18:59:52
Message-ID: c2d9e70e0601051059x41c35365ra5ac10a084c5721f@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/5/06, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Am Donnerstag, 5. Januar 2006 17:01 schrieb Scott Marlowe:
> > The C stands for consistency. Consistency means that only valid data
> > can be written to the database. MySQL fails this test precisely because
> > it does / can write inconsistent data to the database. Note that even
> > the latest version, 5.0.xx, by default, inserts a truncated number on
> > overflow.
>
> That's not at all what the C is about. The C criterion means that a
> transaction transfers the database from one consistent state to another. To
> my knowledge, MySQL does that. On its way there, it silently alters data
> that would violate this consistency criterion, but this does not affect the
> fulfillment of the ACID criteria.
>

so the problem is that MySQL _forces_ a consistent state but in the
process it violates the integrity of the data

--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2006-01-05 19:06:52 Re: Drop database/create database broken in 7.4?
Previous Message MARCELO_LIMA/Blnet 2006-01-05 18:28:06 Autocommit in Fedora 3