First of all, thanks Dieter, that answered my question 1. Now I've got a more serious problem. I have a CMF Document that wraps a PageTemplate object (it does not extend PageTemplate, but internally stores a PageTemplate instance). It looks like when some revision of my object is retreived from ZODB, this does not include the wraped persistent objects that my object may contain. For example, rev1._get_pt.read() and rev2._get_pt.read() always return the HTML of the current revision's wraped PageTemplate. (_get_pt() returns the wraped PageTemplate object) Is there a workaround for this ? The only thing I can think of is storing the PageTemplate HTML at my object level each time it is changed, but that means storing the HTML twice in ZODB... I tried it, and of course it works. Pascal ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************
On Mon, 2005-01-24 at 09:15 +0100, Pascal Peregrina wrote:
First of all, thanks Dieter, that answered my question 1.
Now I've got a more serious problem. I have a CMF Document that wraps a PageTemplate object (it does not extend PageTemplate, but internally stores a PageTemplate instance).
It looks like when some revision of my object is retreived from ZODB, this does not include the wraped persistent objects that my object may contain.
For example, rev1._get_pt.read() and rev2._get_pt.read() always return the HTML of the current revision's wraped PageTemplate. (_get_pt() returns the wraped PageTemplate object)
Is there a workaround for this ? The only thing I can think of is storing the PageTemplate HTML at my object level each time it is changed, but that means storing the HTML twice in ZODB... I tried it, and of course it works.
The only workaround I see right now is to get the list of historic versions for the subobject too, then select the version which timestamp is just below or equal to the timestamp of the container objects historical version. Maybe I add something like that to the historical patch for folders. Regards Tino
Tino Wildenhain wrote at 2005-1-24 10:34 +0100:
... The only workaround I see right now is to get the list of historic versions for the subobject too, then select the version which timestamp is just below or equal to the timestamp of the container objects historical version.
Maybe I add something like that to the historical patch for folders.
I have something like a historical connection. It does not help with the history merging but it helps to present a consistent view once you have chosen a time you are interested in. -- Dieter
Am Montag, den 24.01.2005, 19:27 +0100 schrieb Dieter Maurer:
Tino Wildenhain wrote at 2005-1-24 10:34 +0100:
... The only workaround I see right now is to get the list of historic versions for the subobject too, then select the version which timestamp is just below or equal to the timestamp of the container objects historical version.
Maybe I add something like that to the historical patch for folders.
I have something like a historical connection.
It does not help with the history merging but it helps to present a consistent view once you have chosen a time you are interested in.
Sounds interesting! Where can I see it? :-) Regards Tino
Tino Wildenhain wrote at 2005-1-24 19:56 +0100:
Am Montag, den 24.01.2005, 19:27 +0100 schrieb Dieter Maurer: ...
I have something like a historical connection.
It does not help with the history merging but it helps to present a consistent view once you have chosen a time you are interested in.
Sounds interesting! Where can I see it? :-)
Attached. -- Dieter
Pascal Peregrina wrote at 2005-1-24 09:15 +0100:
... Now I've got a more serious problem. I have a CMF Document that wraps a PageTemplate object (it does not extend PageTemplate, but internally stores a PageTemplate instance).
It looks like when some revision of my object is retreived from ZODB, this does not include the wraped persistent objects that my object may contain. ...
Indeed: each persistent object has its own independent history.
Is there a workaround for this ?
When you have complex objects (consisting of several persistent objects), you must merge the histories of the components or select one (major) component to define the history of the compound. -- Dieter
participants (3)
-
Dieter Maurer -
Pascal Peregrina -
Tino Wildenhain