gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] Corrupt database


From: Jerzy Luszawski
Subject: Re: [Gnumed-devel] Corrupt database
Date: Fri, 31 May 2013 23:37:59 +0200

On 31-05-2013 07:37 "Busser, Jim" <address@hidden> wrote:

> >> Would it make sense to automate this check of fingerprints as part of the 
> >> backup procedure?
> > 
> > Refuse to back up and/or restore if there is a database mismatch ?
> 
> The above could keep a record of when something about the database had been 
> changed. This could help someone to target a date or range of dates when they 
> might have been in communication with someone about a problem that they were 
> having with their database, and may point them to the change that they had 
> made (such as altering a constraint) which they can no longer recall what 
> they did.

If someone messes up so deep with database as to alter a constraint he
should better know enough to backup and double check the results and not
rely on automatic check in client software. 
The application should be end-user-fool-proof and not
maintainer-fool-proof.

-- 
Pozdrawiam,
Jerzy Luszawski



reply via email to

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