Re: [ZODB-Dev] Passing thought: It would be interesting at the application level to have a measure of database record size
On 05/12/2010 01:11 PM, Jim Fulton wrote: It occurs to me that it would be useful, at the application level, to have some measure of an object's record size. This would, for example, be a better basis for OOBucket splits than item count. I thought we gained such an _p_ attribute as an indicator for the size-based cache? -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ 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
Re: [ZODB-Dev] Passing thought: It would be interesting at the application level to have a measure of database record size
On Fri, May 14, 2010 at 4:27 AM, Christian Theune c...@gocept.com wrote: On 05/12/2010 01:11 PM, Jim Fulton wrote: It occurs to me that it would be useful, at the application level, to have some measure of an object's record size. This would, for example, be a better basis for OOBucket splits than item count. I thought we gained such an _p_ attribute as an indicator for the size-based cache? Nope. I also realized that this wouldn't easily help the bucket split case, because the size wouldn't be affected by growth since the last database load or save. Jim -- Jim Fulton ___ 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
