Florent Guillaume wrote:
Andreas Jung wrote:
ToDo: in-place conversion of persistent ZPT instance through
setstate() or so...
Could we avoid doing things in __setstate__ please? It imposes a runtime
cost that doesn't disappear.
I'd rather have a one-time update method that trawls the database, like
is done for Python Scripts recompiling for instance. Or I can call it
myself in my upgrade procedures on the exact objects I know will need
updates.
Perhaps we can use the generations framework.
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org
_______________________________________________
Zope-Dev maillist - [email protected]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
