On Sun, Oct 16, 2011 at 3:01 PM, Mariano Martinez Peck < [email protected]> wrote:
> > > On Sun, Oct 16, 2011 at 2:03 PM, Stéphane Ducasse < > [email protected]> wrote: > >> Mariano I think that the point that Philippe (our national butcher) is >> trying to make is the following: >> If by design a serializer takes the perspective that it will be able to >> load old formats and ensure >> evolution all the time then you have a really cool serializer. >> > > Yes, I know. The problem is if it is worth it. The effort of providing such > feature could be too much in compare to just load a previous version, > materialize, load new version, and serialize again. > > >> >> Now why in fuel it is not possible to have >> FuelMaterializer load: aFile >> >> load using the default = current format >> >> >> FuelMaterializer load: aFile asOfVersion: 1.4 >> Of course this can be much slower but when you want to load data of >> the past you are just happy that this is >> working. >> >> So would not be possible to >> milestone formats >> get the default working fast >> get old version loading slowler but loading. >> >> > It sounds easy, but at least from what I can see this is very complicated. > Do you know a serializer that support this? Lets clarify with an example: > > (of course, without putting all along the code IFs like (version > 2) ifTrue: [blabla] ) > I serialize graph X with Fuel 1.4 in Pharo 1.1. > Then I am in Pharo 1.3 with Fuel 1.7 and I want to materialize X. Fuel 1.4 > doesn't load anymore in Pharo 1.3, so you have to use Fuel 1.7. > So you want to be able to take Fuel 1.7 and materialize X "using version > 1.4" without even loading 1.4 (because it doesn't load) ? > > Thanks > > > >> Because then we get a win win situation. >> Stef >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com
