Comments on: Recombining ZODB storages http://david.wglick.org/2009/recombining-zodb-storages/ Fri, 30 Jul 2010 20:28:30 +0000 http://wordpress.org/?v=2.2.3 By: davisagli http://david.wglick.org/2009/recombining-zodb-storages/#comment-8968 davisagli Sun, 14 Mar 2010 15:24:44 +0000 http://david.wglick.org/2009/recombining-zodb-storages/#comment-8968 @Jean: We routinely create a separate filestorage for each site, for the same reasons you describe. We've never had trouble with cross-references except when we were using several filestorages for the *same* site. (Any of our clients only has access to one site, and our staff knows not to copy and paste between sites.) @Jean: We routinely create a separate filestorage for each site, for the same reasons you describe. We’ve never had trouble with cross-references except when we were using several filestorages for the *same* site. (Any of our clients only has access to one site, and our staff knows not to copy and paste between sites.)

]]> By: Jean Jordaan http://david.wglick.org/2009/recombining-zodb-storages/#comment-8967 Jean Jordaan Sun, 14 Mar 2010 15:10:49 +0000 http://david.wglick.org/2009/recombining-zodb-storages/#comment-8967 When is a good time to split ZODB? I want to have a filestorage per Plone instance. Reasons are that each Plone is backed up seperately, and they're easy to move to another Zope if I get the urge. I can also easily see which ones are biggest. However if they're going to cause breakage with cross-database cut'n'paste, it may be a bad idea. When is a good time to split ZODB? I want to have a filestorage per Plone instance. Reasons are that each Plone is backed up seperately, and they’re easy to move to another Zope if I get the urge. I can also easily see which ones are biggest. However if they’re going to cause breakage with cross-database cut’n'paste, it may be a bad idea.

]]> By: davisagli http://david.wglick.org/2009/recombining-zodb-storages/#comment-6664 davisagli Thu, 10 Dec 2009 15:55:34 +0000 http://david.wglick.org/2009/recombining-zodb-storages/#comment-6664 ZODB 3.8 doesn't throw KeyErrors while packing anymore if it encounters cross-references, but it still isn't smart enough to keep from garbage collecting an object that is only referenced from another database. For that you need zc.zodbdgc, I think. In ZODB 3.9 there is an option to disallow cross-references entirely in the first place. ZODB 3.8 doesn’t throw KeyErrors while packing anymore if it encounters cross-references, but it still isn’t smart enough to keep from garbage collecting an object that is only referenced from another database. For that you need zc.zodbdgc, I think. In ZODB 3.9 there is an option to disallow cross-references entirely in the first place.

]]> By: amleczko http://david.wglick.org/2009/recombining-zodb-storages/#comment-6663 amleczko Thu, 10 Dec 2009 15:41:53 +0000 http://david.wglick.org/2009/recombining-zodb-storages/#comment-6663 what about using ZODB 3.8.x? It handles multi-references quite well what about using ZODB 3.8.x? It handles multi-references quite well

]]> By: Linux_Blade_guy http://david.wglick.org/2009/recombining-zodb-storages/#comment-6596 Linux_Blade_guy Thu, 03 Dec 2009 15:09:50 +0000 http://david.wglick.org/2009/recombining-zodb-storages/#comment-6596 You are my hero, seriously!! I inherited a Plone site with exactly this scenario - the portal_catalog has been split in to another database, I get 'n' key errors when packing and it's had POSKeyError problems in the past. Haven't tried out your solution yet but this is the first bit of info I've seen that both explains the problem and tells what to do about it! You are my hero, seriously!!

I inherited a Plone site with exactly this scenario - the portal_catalog has been split in to another database, I get ‘n’ key errors when packing and it’s had POSKeyError problems in the past.

Haven’t tried out your solution yet but this is the first bit of info I’ve seen that both explains the problem and tells what to do about it!

]]>