Jim Fulton wrote:
> Yup, where I assume you mean using the in-use storage as input. The
> script makes a new copy.  After making the copy, you can change the
> server to use that. Of course, changes made after copying won't be in
> the copy, but if you just want to try the script out, you can just
> point it at an in-use file. I did.

Initial testing suggests this works just fine :-)

I used the following buildout to get the right version of ZODB in 
isolation and so didn't have to worry about affecting either the old or 
new Zope instances involved:

[buildout]
parts =
   fixer
versions = versions

[versions]
ZODB3 = 3.8.3b1

[fixer]
recipe = zc.recipe.egg
eggs = ZODB3

cheers,

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
            - http://www.simplistix.co.uk
_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev

Reply via email to