Re: [Gnumed-devel] Re: versioning scheme

[Karsten Hilbert]

All this discussion about a number which does not have any external meaning.

There will never be a database "release" without a client release. What for 
would there ?

The client undergoes way longer development before release than the database it 
requires. Hence
the db schema is way longer tested.

Of course, there WILL be schema problems at some point, say, a function not 
working
correctly. Such will be corrected by a few change scripts applied to the 
appropriate database.
In order for the local people to find out the state they can look at the 
appropriate table which
tells them which change scripts have been applied or not.

So,  a new database "release" will only ever be released with a client - if at 
all.

Client 1.2 and client 1.3 may not require changes to the database. So the 
database schema will
stay at version 145. Simple as that.

In fact, the v8, v9 whatnot are nothing but pretty labels. Basically they are 
just convenient ways to *name* the database (as could be done any other way 
without merit). The heart of the matter lies
in the md5 sum over the base tables.

Again, the client will tell you which database it expects, it will tell you 
which database it finds and
it will refuse to connect to a database it does not expect but finds.

Dead simple.

Now, please someone file a wishlist item:

 "add -v / --version CLI option showing client version, db version, db hash"

And another one:

 "in gmPG2.py add map_client_version2database_version and remove 
curr_db_version from
   gmGuiMain.py and utilize the mapping where needed"

This will keep the mapping in one place and more easily maintainable.

Thanks,
Karsten

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: 
http://www.gmx.net/de/go/multimessenger