Sure, you can lock the one ZODB, but depending on your apps, you will get a lot of errors (all of my apps write to the ZODB). I have outlined what I do here: http://www.zopezone.com/faq/1063992383 Jake -- http://www.ZopeZone.com Edward Pollard said:
We're moving some content from Zope 2.6 to 2.6.2, and I'm wondering what the best way to do this would be.
In the fantasy world that is my mind, I think I'd be looking for a way to safely lock the ZODB in the 2.6 instance, so we can migrate to 2.6.2 while still serving (unchangeable) content from 2.6.
Does such a concept exist?
--- Edward J. Pollard University of Lethbridge Web Development
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )