Actually the database format is versioned already (one of the big things we did in this release was make that possible) and so we can read 0.6.0 databases with the 0.6.1 code base in order to upgrade. As you say, I wasn't going to add a new version of the database format just to read alpha release databases, and so my question was to see if it was a big problem for someone. If it were, I might consider adding the serialization scheme you suggest (dump xml or s- expressions similar to cl-prevalence) to the current release. However it's taken too long already so I'd like to dispense with that and implement it later. That would be a good ticket to add the Trac database (http://trac.common-lisp.net/elephant) if you'd like to do so. Although there may already be one there if you want to check first.

Ian

On Mar 16, 2007, at 2:27 PM, Pierre THIERRY wrote:

Scribit Ian Eslick dies 16/03/2007 hora 10:53:
For various reasons I need to renumber the type tags which means that
existing 0.6.1 databases will  not be properly deserialized.

Coudln't the database format be versioned? We could then keep apart the
code that work on a given version, to always be able to deserialize
it... For such alpha versions it's obviously not worth the effort in the
long term, but for stable releases it would probably be great.

That would also be a strong argument to use Elephant, as users would not
have to be afraid of losing their data.

Or maybe an alternative would be to provide some verbose and inefficient serialization scheme that could be used as an intermediary when changing
a database version...

Doubtfully,
Pierre
--
[EMAIL PROTECTED]
OpenPGP 0xD9D50D8A
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel

Attachment: PGP.sig
Description: This is a digitally signed message part

_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel

Reply via email to