Re: 'Official' definition of ACID compliance?
От | Jaime Casanova |
---|---|
Тема | Re: 'Official' definition of ACID compliance? |
Дата | |
Msg-id | c2d9e70e0601051059x41c35365ra5ac10a084c5721f@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 'Official' definition of ACID compliance? (Peter Eisentraut <peter_e@gmx.net>) |
Ответы |
Re: 'Official' definition of ACID compliance?
|
Список | pgsql-general |
On 1/5/06, Peter Eisentraut <peter_e@gmx.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 ;)
В списке pgsql-general по дате отправления: