Re: [Gramps-devel] Database change

[James G. S. (jim) <jg...@sa...>]

Zsolt Foldvari wrote:
> Since r10410 in trunk we've got a new version of the database (v14).
> This means that a db created or edited with the trunk version cannot be
> opened with the gramps30 branch version anymore.
> 
>

Just curious:

I see that src/gen/db/dbdir.py has new code gramps_upgrade_14() to
accomplish the migration from 13-to-14, I presume.

I also see code in src/GrampsDbUtils/_GrampsBSDDB.py for version upgrade
steps from <10 to 13.

  Aside: I'm guess upgrades so far haven't been so numerous or
  complex that they couldn't all be maintained in current code.
  At some point, of course, that may change -- I don't know how
  far away that might be. I favor *not* implementing solutions
  to problems before discovering the requirements. ;-)

Is there any actual policy on implementing upgrade code?

Has there been any past experience that would be good to document?

Is there any developer (or user) documentation dealing with version
upgrades (generally) on the wiki?

Also, what, exactly, justifies a database version change -- certainly
structure changes, but what about a change in valid data values? I'm
thinking about the small issue of retiring the EventEype CAUSE_DEATH;
would something like that justify a db version change?

It seems to me that some guidelines on the wiki would be useful.

Regards,
..jim