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

Durus standard backend defines a "gen_oid_record()" method that gives a
generator that iterates over all registers in the storage. This is used,
I suppose, to upgrade object classes when necessary. Or to do backups.

Problem is, if during the "gen_oid_record()" the client does an object
commit, my BerkeleyDB backend storage can't garantee that the iterator
doesn't skip an object or gives an already visited object.

So my question is: How is currently the usage pattern of
"gen_oid_record()"?. In particular, does the client object commit to the
storage while iterating over the storage content?

Thanks in advance.

- --
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

iQCVAwUBRENv0Jlgi5GaxT1NAQI4KwQAl7c2BlItF+qMqtDr5DhXJp+nemILozqr
5k0tmTKDuXo4P3yrrU3YALcRJMswSTyLv/i+cAd5h1JoXW1EjJSmkoakK0iemqoU
oodvv9y6jo+/KaNSzI+8i/EPTkxi0FnGRlZ7bI7Jorkyer5w8UPC78reQ4zp72hl
lh8JFb1ooWs=
=7xfJ
-----END PGP SIGNATURE-----