> > > 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.
for a serializer I think that it is worth it. I once used a backup system which used a private format for my archives and I lost them since it was discontinued.... > > > 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: > > 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) ? Yes what I want to say is that if evolution is the key then you have to be explicit about milestones and version and in the end this is excellent. But of course you get a cost and effort. But this means that after that there is no more other serializer. I think that it is also a nice way to get meta about the format. Stef > > Thanks > > > Because then we get a win win situation. > Stef > > > > -- > Mariano > http://marianopeck.wordpress.com >
