Hello, I have an export file of objects (that come from a Plone 2.0.5 instance). Unfortunately, the products are not compatible with a newer Plone version. I'm building a new version of this product (but it will be quite different from the initial one). I'm wondering if it is possible to load datas for a zexp file without the old product and then build new instances of my new product. That is why I'd like to know if there is a good documentation concerning the internal structure of zexp files. Thanks in advance Sebastien
--On 8. Juni 2006 14:28:31 +0200 Sébastien VINOT <sebastien.vinot@logisphere.fr> wrote:
I'm wondering if it is possible to load datas for a zexp file without the old product and then build new instances of my new product. That is why I'd like to know if there is a good documentation concerning the internal structure of zexp files.
The .zexp files are Python pickles. The XML generated through export/import is basically an XML representation of the Python pickle. The most straight forward solution would be to write a migration script for your stuff and not to look into pickles...but you can of course follow the pickle road if you like it the hard way :-) -aj -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info@zopyx.com - Phone +49 - 7071 - 793376 E-Publishing, Python, Zope & Plone development, Consulting
-----Message d'origine----- De : Andreas Jung [mailto:lists@zopyx.com] Envoyé : jeudi 8 juin 2006 14:38 À : Sébastien VINOT; zope@zope.org Objet : Re: [Zope] Export format documentation
--On 8. Juni 2006 14:28:31 +0200 Sébastien VINOT <sebastien.vinot@logisphere.fr> wrote:
I'm wondering if it is possible to load datas for a zexp
file without
the old product and then build new instances of my new product. That is why I'd like to know if there is a good documentation concerning the internal structure of zexp files.
The .zexp files are Python pickles. The XML generated through export/import is basically an XML representation of the Python pickle. The most straight forward solution would be to write a migration script for your stuff and not to look into pickles...but you can of course follow the pickle road if you like it the hard way :-)
-aj
You're right, I did not think about XML : thanks for the very good idea ! Sebastien
--On 8. Juni 2006 14:44:39 +0200 Sébastien VINOT <sebastien.vinot@logisphere.fr> wrote:
I'm wondering if it is possible to load datas for a zexp
file without
the old product and then build new instances of my new product. That is why I'd like to know if there is a good documentation concerning the internal structure of zexp files.
The .zexp files are Python pickles. The XML generated through export/import is basically an XML representation of the Python pickle. The most straight forward solution would be to write a migration script for your stuff and not to look into pickles...but you can of course follow the pickle road if you like it the hard way :-)
-aj
You're right, I did not think about XML : thanks for the very good idea !
Possibly my reply wasn't clear enough. The pickle format (binary or XML) appears too low-level in order to write a reasonable migration script. The recommended solution would be to write a reasonable migration on the application level based on your current data... -aj
-----Message d'origine----- De : Andreas Jung [mailto:lists@zopyx.com] Envoyé : jeudi 8 juin 2006 14:48 À : Sébastien VINOT; zope@zope.org Objet : Re: RE : [Zope] Export format documentation
--On 8. Juni 2006 14:44:39 +0200 Sébastien VINOT <sebastien.vinot@logisphere.fr> wrote:
I'm wondering if it is possible to load datas for a zexp
file without
the old product and then build new instances of my new product. That is why I'd like to know if there is a good documentation
concerning
the internal structure of zexp files.
The .zexp files are Python pickles. The XML generated through export/import is basically an XML representation of the Python pickle. The most straight forward solution would be to write a migration script for your stuff and not to look into pickles...but you can of course follow the pickle road if you like it the hard way :-)
-aj
You're right, I did not think about XML : thanks for the very good idea !
Possibly my reply wasn't clear enough. The pickle format (binary or XML) appears too low-level in order to write a reasonable migration script. The recommended solution would be to write a reasonable migration on the application level based on your current data...
-aj
That's right I misunderstood your answer. Thanks for your explanations. Sebastien.
On Thu, Jun 08, 2006 at 02:54:10PM +0200, S?bastien VINOT wrote:
De : Andreas Jung [mailto:lists@zopyx.com] Possibly my reply wasn't clear enough. The pickle format (binary or XML) appears too low-level in order to write a reasonable migration script. The recommended solution would be to write a reasonable migration on the application level based on your current data...
actually the XML format can sometimes be quite usable. maybe not for images :) -- Paul Winkler http://www.slinkp.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sébastien VINOT wrote:
Hello,
I have an export file of objects (that come from a Plone 2.0.5 instance). Unfortunately, the products are not compatible with a newer Plone version. I'm building a new version of this product (but it will be quite different from the initial one).
I'm wondering if it is possible to load datas for a zexp file without the old product and then build new instances of my new product. That is why I'd like to know if there is a good documentation concerning the internal structure of zexp files.
Thanks in advance
If you do the export to XML, rather than the binary pickle format of a zexp file, then you should be able to examine the structure in an editor, and even (in theory, anyway), transform it into a form compatible with your new product version. YMMV as to whether the effort here outweighs writing BBB / migration code in your product. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEiBt3+gerLs4ltQ4RAs2OAJ9/dTJSQnVRm6w0ylmAp85lXS/SGACfa9+e Mnd23flUKTH1nbYihJm3jr0= =sKwl -----END PGP SIGNATURE-----
participants (4)
-
Andreas Jung -
Paul Winkler -
Sébastien VINOT -
Tres Seaver