Re: [ZODB-Dev] Database size increase on commit()

2007-11-22 Thread tsmiller
jürgen Kartnaller-2 wrote: > > > > tsmiller wrote: >> Thanks. The changes that you suggested work. I think that what I did >> not >> see is that one key = one btree. I was trying to store multible stores >> under a single btree ie.. >> dbRoot['books'] = bTree.OOBTree() >> dbRoot['books']['s

Re: [ZODB-Dev] Database size increase on commit()

2007-11-22 Thread tsmiller
Thanks. The changes that you suggested work. I think that what I did not see is that one key = one btree. I was trying to store multible stores under a single btree ie.. dbRoot['books'] = bTree.OOBTree() dbRoot['books']['store1'] = {} dbRoot['books']['store2'] = {} dbRoot['books']['store3'] = {

Re: [ZODB-Dev] Database size increase on commit()

2007-11-21 Thread tsmiller
Tres Seaver wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > tsmiller wrote: > >> This is what my gut feeling was telling me. Before I knew ANYTHING about >> the ZODB it seemed natural and easy to just use dictionaries as data >> structures for things such as accounts, books, di

Re: [ZODB-Dev] Database size increase on commit()

2007-11-21 Thread tsmiller
Tres Seaver wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > tsmiller wrote: >> ZODB guys, >> >> I have discovered the following. >> >> db.dbRoot is the root of my database and 'accounts' is a key. I simply >> want to set a timestamp for when a user logs in. I make the timest