gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] auto-altering "old" gnumed databases to be read-only
Date: Wed, 17 Jun 2009 23:11:42 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Wed, Jun 17, 2009 at 01:36:26PM -0700, Jim Busser wrote:

> 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"

Yes, both is possible. But it may not be desired to auto-set
it to readonly.

> Advantages might be:
> 
> - protects production systems from oversights (human
>   error) on the part of IT_help

I am not entirely sure what you mean ?  It is not always
desirable to automatically set the old database read only -
for example if IT_help is simply testing upgrade procedures.

> - 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)

IT_help could do that manually IF so desired.

> - 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

Said doctor could only meaningfully access it for reading
and it would only be up to date until the moment when the
new database was created. Anything written into the old
database would, of course, not be available in the new
database.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346




reply via email to

[Prev in Thread] Current Thread [Next in Thread]