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

David Binger wrote:
> Yes, but you suggested this be done by inspection/clearing of attributes
> on the newly created objects.  It seems better to record oids given out
> as the transaction is serialized in the end() call.

Excuse me. I was just defending the general idea of reusing "lost" OIDs
when a conflict arises. I haven't look at the code lately, but seems a
fairly trivial improvement.

>> In fact I have also "patched" durus to allow clients to be notified when
>> certain objects are modified. So I provide also a publish&subscribe
>> paradigm :-).
>
> Your clients are "smarter" than mine.

Most of my "clients" are dull programs :-).

> Do you have a procedure for managing schema/code change?

No. I haven't needed it yet. I know about Schevo, but never examine it
deeply. In fact I reached Durus via Schevo };-).

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

iQCVAwUBRGzPXplgi5GaxT1NAQK6hQP/XL/3eMrIudq6jYXaBL0jrmncZv8TGapN
8pGBt1jAmhGN7Xl+s5ro94YdsCcMKaM6h9Ej7Rcv6uKkGKrekfDvpnwOs6XVPd/z
dHAJv7wKgdnSQPvcAH0fLgTD2IhMCcT0C6cOM955rVklMOySykNKPGStru+poAI4
K9bHtgq2oKY=
=jfib
-----END PGP SIGNATURE-----