| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | 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:20:31 |
| Message-ID: | 200601051920.31686.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MARCELO_LIMA/Blnet | 2006-01-05 18:28:06 | Autocommit in Fedora 3 |
| Previous Message | F. Fernandez | 2006-01-05 18:02:15 | java.sql.SQLException: ERROR: invalid byte sequence for encoding "UNICODE": 0xe3936e |