-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Neil Schemenauer wrote:
>> So does Durus Storage Server give a "degree 3 isolation"?. That would be
>> a very good point.
>
> If it doesn't then there is a bug.  Each client remembers the OIDs
> of objects it has seen during a transaction.  When the client tries
> to commit, it first receives a set of invalid OIDs from the server
> (OIDs for objects that have been changed in the DB).  If any of
> those OIDs have been seen then a conflict error is raised.

Uhmmm. I'm confused.

I think durus will raise a conflict if you have the remotely modified
object in your cache, EVEN if you didn't accessed that object in current
transaction. Some experiments seems to confirm that idea. I think this
is an issue to improve in future Durus releases. That is, "false" conflicts.

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea@argo.es http://www.argo.es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea@jabber.org         _/_/    _/_/          _/_/_/_/_/
                               _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBREqCw5lgi5GaxT1NAQKrLQP/SCzkGj6FSfZrdz9LlA6nhpuADFC9msDZ
NZ9x3MyJNEdl2JIxbgtchGKTKFcoweHgxW+ctXceVDfYGJwtYiYiU0SO6101haoT
nXgObyEwxx1v9hFizM8hn7AIf6Z9qR97FNtnomAMy/QR9G+T/JcvWLdH8wz7idI5
56ueNHPm6Mc=
=fWd2
-----END PGP SIGNATURE-----