[ZODB-Dev] Database size increase on commit()
tsmiller
tsmiller at gnixterhouse.com
Thu Nov 22 12:48:30 EST 2007
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']['store1'] = {}
>> dbRoot['books']['store2'] = {}
>> dbRoot['books']['store3'] = {}
>> etc...
>> I was thinking that you would have a single btree that kept everything.
>> But
>> it looks like I have to do the following, which will mean that I will
>> have
>> many btrees in my program. Is this correct thinking?
>> dbRoot['books']['store1'] = bTree.OOBTree()
>> dbRoot['books']['store2'] = bTree.OOBTree()
>> dbRoot['books']['store3'] = bTree.OOBTree()
>>
>> So is it correct that you have (one key = one bTree) relationship?
>
> Right
>
> Instead of using dicts you use btrees.
>
> _______________________________________________
> For more information about ZODB, see the ZODB Wiki:
> http://www.zope.org/Wikis/ZODB/
>
> ZODB-Dev mailing list - ZODB-Dev at zope.org
> http://mail.zope.org/mailman/listinfo/zodb-dev
>
>
Thanks. Case solved. Sometimes just getting the thing started rolling is
the hardest part. :-)
--
View this message in context: http://www.nabble.com/Database-size-increase-on-commit%28%29-tf4852044.html#a13900703
Sent from the Zope - ZODB-Dev mailing list archive at Nabble.com.
More information about the ZODB-Dev
mailing list