> In repoze.catalog documentation, I read :
>
> """
> Note that when you call index_doc, you pass in a docid as the first
> argument, and the object you want to index as the second argument. When
> we index the peach object above we index it with the docid 1. Each docid
> must be unique within a catalog; when you query a repoze.catalog
> catalog, you’ll get back a sequence of document ids that match the query
> you supplied, which you’ll presumably need to map back to the content
> object in order to make sense of the response; you’re responsible for
> keeping track of which objects map to which document id yourself.
> """
> Url : http://docs.repoze.org/catalog/overview.html#indexing
>
> "you’re responsible for keeping track of which objects map to which
> document id yourself." => it is this part I would like to implement.

This last part is handled by zope.intid package, which is used internally
by zope.catalog.
When a persistent IntId utility has been created and registered, you can
do what you need :
 - get a unique ID (an integer) for a given object (when persisted !)
 - get an object for a given ID

Regards,
Thierry


_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev

Reply via email to