Dieter Maurer wrote:
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.
I've implemented the setstate() variant as
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
--On 5. Januar 2006 17:36:45 +0100 Florent Guillaume [EMAIL PROTECTED] 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
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
Andreas Jung wrote at 2006-1-5 17:44 +0100:
...
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.
I've implemented the
