Re: [Gnumed-bugs] Unhandled exception where encounter duration was not 'sane'

[Karsten Hilbert]

On Thu, Oct 16, 2014 at 12:08:47PM +0200, Karsten Hilbert wrote:

> Close scrutiny of the log snippet shows why the UPDATE fails
> (but not quite yet how it ended up that way):
> 
> > 2014-10-15 15:20:09  ERROR     gm.db 
> > (/Users/djb/Downloads/gnumed-client.1.4.9/Gnumed/pycommon/gmPG2.py::run_rw_queries()
> >  #1365): RW query failed: [UPDATE clin.encounter SET
> >                             started = cast('2014-10-15T11:30:00-07:00' as 
> > timestamp with time zone),
> 
> Note the "Oct 15th" ...
> 
> >                             last_affirmed = 
> > cast('2014-10-14T12:30:00-07:00' as timestamp with time zone),
> 
> ... vs the "Oct 14th".

In retrospect this seems to establish that GNUmed is "doing
the right thing" -- which relieves us from having to rush out
a new release just before the Debian Freeze.

However, I agree this condition could be handled much more
gracefully.

Karsten
-- 
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346