On Fri, 2008-10-03 at 15:57 +0300, Markus Läll wrote:
> I think I know now -- objects compare identical and equal only if they are
> in the same container object. (Check the code below)
> I don't mean to be negative, but why can't ZODB be like a big RAM? Like
> when i store an object to multiple places on the same DB, then it would
> actually be the same in each place. (Like if you comment out the "Commit,
> close and reload" part of the below code, all the comparisons evaluate to
> True)

It does, you just need to do a little more work. See below.

> # -*- coding: cp1252 -*-
> # ZODB
> from ZODB import FileStorage, DB
> import transaction
> # Trees
> from BTrees.IOBTree import IOBTree as IO
> from BTrees.OOBTree import OOBTree as OO, OOSet as OSet
> # Open db
> storage = FileStorage.FileStorage('test.fs')
> db = DB(storage)
> conn = db.open()
> root = conn.root()
> # The  one and only class
> class X(object):
Here's the Deal: ZODB is pretty much transparent. However, to work its
full magic, your objects have to subclass `persistent.Persistent`.
Otherwise ZODB will only pickle them in one large database record and
thus not know about their identity anymore. Also, object changes won't
trigger persistency updates automatically.

Your example will work as soon as you change this to:

class X(persistent.Persistent):


Christian Theune · [EMAIL PROTECTED]
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1
Zope and Plone consulting and development

Attachment: signature.asc
Description: This is a digitally signed message part

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -  ZODB-Dev@zope.org

Reply via email to