[Gnumed-devel] auto-altering "old" gnumed databases to be read-only

[James Busser]

On the wiki page ServerUpgrade2 we have a section "A final, but important, 
production note" where we suggested

   * depending if it is desired to keep the old database available, reconfigure 
it to not allow any further connections and/or remove or control the copies of 
the client that would point to it

... is it possible for the server upgrade script to take account of the 
database version that is going to now be "old" and
- reconfigure it, so that it will afterward be read-only
- update its banner record, to say
    "this database is superceded by a newer
     version, and is now read-only"

Advantages might be:

- protects production systems from oversights (human error) on the part of 
IT_help
- protects production systems from users who were able to hide their old 
clients from IT_help (for example on laptops that were not regularly brought 
into the praxis)
- permits the old system to remain available, in case a doctor had to access it 
from home before they could properly update their home computer or laptop with 
a new client