[Gnumed-devel] post-final schema bug handling scenario (was 0.3-rc4 released)

[James Busser]

On 18-Aug-08, at 9:32 AM, Rogerio Luz wrote:

In case a bug is discovered in what is currently thought to
be the final gnumed_v9 schema which is included in the
v9.rcX preliminary server tarballs there will then be a need
to "fix" that database. This will be done by some sort of
script changing the database to whatever it should be.

This is, however, NO DIFFERENT from when that need arises
*after* we release _v9 properly ...

I am 99.99% sure there will not be a need to change the
basic table structure which actually *stores* the data.
Anything that might exhibit a bug will most likely be in the
"dynamic" part - rules, triggers, functions, views - nothing
that really changes the data itself so the "fix" will be
non-modifying as far as the data itself is concerned.

I was thinking to add some or all of the above to the wiki page

http://salaam.homeunix.com/bin/view/Gnumed/ServerInstallUpgrade

except that presently this page describes the scripts as

GNUmed will upgrade the database stepwise only, say, from v7 to v8.

- Example upgrading the gnumed_v7 to gnumed_v8 (current stable database):

 sh upgrade-db.sh 7 8 

The versions must be consecutive. 

Would the fix be deployed as a minor update within the same script that is already used for major update / upgrades:

net_upgrade-gnumed_server.sh

and would we envision the maintainer to run a command line call like

 sh upgrade-db.sh 8 8_1