Search Postgresql Archives

Re: 'Official' definition of ACID compliance?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux