gnumed-bugs
[Top][All Lists]
Advanced

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

Re: [Gnumed-bugs] [Gnumed-devel] GNUmed 1.4.2 Maintenance Release


From: Karsten Hilbert
Subject: Re: [Gnumed-bugs] [Gnumed-devel] GNUmed 1.4.2 Maintenance Release
Date: Thu, 28 Nov 2013 09:45:25 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Nov 28, 2013 at 02:37:37AM +0000, Jim Busser wrote:

> > *** BUT *** I now see that
> > 
> >     all 467 rows in my clin.episode
> > 
> > and
> > 
> >     nearly all (739 of 742 rows, IOW all but Kirk's) in clin.encounter
> > 
> > now show as modified
> 
> … wondering whether as part of database upgrades, any of the triggers should 
> be disabled in order to not alter every record in the database with a
> 
>       modified by gm-dbo

No.

> which then makes it harder to query the most recent (care-stimulated) 
> modification.

.modified_by does not give any such guarantuee. It is only
-- for lack of a better option -- misused in some places AFAIR.

Those records ARE modified (the .fk_location is set).

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



reply via email to

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