Re: RE : RE : [Zope] Export format documentation

2006-06-08 Thread Paul Winkler
On Thu, Jun 08, 2006 at 02:54:10PM +0200, S?bastien VINOT wrote:
> > De : Andreas Jung [mailto:[EMAIL PROTECTED] 
> > 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
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )


RE : RE : [Zope] Export format documentation

2006-06-08 Thread Sébastien VINOT


> -Message d'origine-
> De : Andreas Jung [mailto:[EMAIL PROTECTED] 
> 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 
> <[EMAIL PROTECTED]> 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.

___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )


Re: RE : [Zope] Export format documentation

2006-06-08 Thread Andreas Jung



--On 8. Juni 2006 14:44:39 +0200 Sébastien VINOT 
<[EMAIL PROTECTED]> 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

pgpKqUCOBca3Y.pgp
Description: PGP signature
___
Zope maillist  -  Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope-dev )