Subject | Re: [ib-support] Understanding Transaction-behaviour |
---|---|
Author | Claudio Valderrama C. |
Post date | 2002-01-25T05:50:28Z |
""Richard Pendered"" <rpendered@...> wrote in message
news:000001c1a4ec$8eaa3100$208282c1@tipadrrp...
Solid (www.solidtech.com) is a typical commercial RDBMS that supports
versioning. I evaluated it briefly after 17-Dec-1999 when all clues were
indicating that IB was finally dead.
MsSql and its parent, Sybase, don't have versioning.
There are OO databases that have supported versioning and configurations (a
snapshot keeping a mesh with all object versions that are interoperable) for
years.
C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing
news:000001c1a4ec$8eaa3100$208282c1@tipadrrp...
> From what I remember about MS SQL 6.5 is that it uses record, row andtable
> locking within its transactions. I presume that it would be the same in 7Not the only.
> and 2k.
> So yes IB/FB are the only RDBMS to use a versioning model.
Solid (www.solidtech.com) is a typical commercial RDBMS that supports
versioning. I evaluated it briefly after 17-Dec-1999 when all clues were
indicating that IB was finally dead.
MsSql and its parent, Sybase, don't have versioning.
There are OO databases that have supported versioning and configurations (a
snapshot keeping a mesh with all object versions that are interoperable) for
years.
C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing