Dieter Maurer wrote:
Christian Theune wrote at 2006-7-13 17:13 +0200:
...
Is there any ability in ZODB to retroactively wrap objects in a
persistence mechanism instead of having to rewrite an entire library
to use the Persistent class?
You can always persist (almost) any object, even if it
Roché Compaan schrieb:
If you have common add/edit methods in your app used by all of your
classes, you could do application level replication between Zopes. We
have written a small replication module for on of our apps that copes
extremely well with disconnected Zopes, and replicates a very
On Fri, 2006-07-14 at 08:58 +0200, Joachim Schmitz wrote:
Roché Compaan schrieb:
If you have common add/edit methods in your app used by all of your
classes, you could do application level replication between Zopes. We
have written a small replication module for on of our apps that copes
No problem, but remember this is app specific and still works with the
ZODB distributed with Zope 2.7.
I recently tweaked it to work with Zope 2.8.7 (remember my query about
self._p_jar._storage._serial a week or two ago?) .. The only change needed
was s/_serial/_tid/ :
def log(self,
I'm trying to detect a disparity between an instance __version__ and a
class __version__, signifying a class upgrade. However, I'm not sure
why the following code doesn't work.
class Foo(Persistent):
__version__ = 1.0
def __setstate__(self, state):
Persistent.__setstate__( self,
On 7/14/06, Chris S [EMAIL PROTECTED] wrote:
I'm trying to detect a disparity between an instance __version__ and a
class __version__, signifying a class upgrade. However, I'm not sure
why the following code doesn't work.
class Foo(Persistent):
__version__ = 1.0
def __setstate__(self,
