Subject | Re: [Firebird-Architect] Re: Special Relativity and the Problem of Database Scalability |
---|---|
Author | Jim Starkey |
Post date | 2010-01-27T12:12:04Z |
Paul RuiZendaal wrote:
1. A transaction sees a constant view of the database plus any
updates performed by the transaction
2. A transaction cannot update or delete a version of a record that
it could not see
3. Primary and unique keys must be guaranteed unique
4. Referential constraints must be honored
What other elements of database consistency need to be maintained
implicitly or explicitly?
--
Jim Starkey
NimbusDB, Inc.
978 526-1376
[Non-text portions of this message have been removed]
>> I don't see the point.Here is a first approximation of consistency rules:
>>
>
> I was thinking about consistency between nodes, which isn't quite the C in
> ACID. As you said, it begins with proper definitions :^)
>
>
1. A transaction sees a constant view of the database plus any
updates performed by the transaction
2. A transaction cannot update or delete a version of a record that
it could not see
3. Primary and unique keys must be guaranteed unique
4. Referential constraints must be honored
What other elements of database consistency need to be maintained
implicitly or explicitly?
--
Jim Starkey
NimbusDB, Inc.
978 526-1376
[Non-text portions of this message have been removed]