[ZODB-Dev] Non versioned objects

[Cyril Elkaim]

The QueueCatalog from Jim seems a very intersting idea. But I must admit 
that
I don't like to cut the database between two different storages.

Actually we have implemented our own Catalog classes. These classes have 
an OOBTree to
contain references to objects and a series of list objects that are used 
as indexes (don't say
it's inefficient, I know :-) . A solution is effectively to put the 
complete Catalogs in the
Berkeley DB and the rest of the objects in the current FileStorage. It's 
not very difficult in
our own case because we are already using GUID for each and every 
object, this is a
necessity because we are moving objects between different databases. And 
they must be
labeled for our purposes.

So I will take a look at QueueCatalog and see how to convert GUID to 
paths if I understand
this thing correctly.

Thanks,
Cyril Elkaim

Toby Dickenson wrote:
> On Wednesday 31 Jul 2002 4:53 pm, Cyril Elkaim wrote:
> 
>>The reason I need this and I asked for is that I maintain Persistent
>>indexes in the ZODB.
>>Each time I add or modify an entry in an index it get duplicated by the
>>transaction.
>>And I don't need this behavior.
> 
> 
> Have you considered using a storage that doesnt support undo, and therefore 
> doesnt keep any history?
> 
> 
> _______________________________________________
> For more information about ZODB, see the ZODB Wiki:
> http://www.zope.org/Wikis/ZODB/
> 
> ZODB-Dev mailing list  -  ZODB-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zodb-dev