On Jul 8, 2005, at 12:51 PM, David Binger wrote:

> On Jul 8, 2005, at 5:03 AM, Thomas Guettler wrote:
>
>>
>> Since Durus is very much like ZODB, this link might help, too:
>>
>> http://www.zope.org/Wikis/ZODB/FrontPage/guide/
>> node6.html#SECTION000630000000000000000
>> "5.3 BTrees Package"
>
>
> Thanks for the link.
>
> I noticed one thing there that would be different in Durus.
> In ZODB, you should never use Persistent instances as keys
> in a BTree because it is not compatible with ZODB's conflict
> resolution.  Durus doesn't attempt any conflict resolution, so
> this restriction isn't mandatory.  I would always prefer
> keys that are really immutable, though.

Hmmn, thanks for pointing that out.

I am using persistent instances **liberally** in btree keys, so a
straight porting to zodb would not work. However, the way my persistent
items are defined, i can very easily get a (humanly descriptive) string
tuple to identify each item.... but, that will add the overhead of
translating of instances to such immutable objects, on all the gets...
well, i guess it can always be another computed attribute ;)

mario