Re: 'Official' definition of ACID compliance? - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: 'Official' definition of ACID compliance?
Date
Msg-id 200601052225.23125.peter_e@gmx.net
Whole thread Raw
In response to Re: 'Official' definition of ACID compliance?  (Scott Marlowe <smarlowe@g2switchworks.com>)
Responses Re: 'Official' definition of ACID compliance?
Re: 'Official' definition of ACID compliance?
List pgsql-general
Am Donnerstag, 5. Januar 2006 21:58 schrieb Scott Marlowe:
> But it's not consistent.  Imagine we do the one where we take one from
> peter and give it to paul.  If paul's account is stored in an int, and
> is at 2147483647, and we add one, it does not increment, and it does not
> cause an error that will force a transaction to roll back.

The effects of the commands on the database are not sensible with respect to
the intent of the commands, but the state of the database is consistent both
before and afterwards with respect to the integrity constraints defined
within the database.  That's what this is all about.  ACID is about
transaction processing, not about SQL data type semantics.

pgsql-general by date:

Previous
From: Joe Audette
Date:
Subject: Re: Suse Linux 10.0
Next
From: ellis@spinics.net (Rick Ellis)
Date:
Subject: Re: Can't connect to postgresql using 'psql -d database -U user -W'