[Top][All Lists]

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

Re: [Gnumed-bugs] <bug>: Error

From: Karsten Hilbert
Subject: Re: [Gnumed-bugs] <bug>: Error
Date: Sun, 17 Apr 2011 23:30:36 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

Hello Joan,

thanks for your report !

> user comment  : Error
> client version: 0.9.1

What you've been trying to do is add a substance intake with
a discontinuation date earlier than the start date which, of
course, is clinically nonsensical and the database saves our

> 2011-04-16 19:19:09  ERROR     gm.db 
> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\logging::exception()
>  #1021): error running RW query
> Traceback (most recent call last):
>   File 
> "C:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outPYZ1.pyz/Gnumed.pycommon.gmPG2",
>  line 1232, in run_rw_queries
>   File 
> "C:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outPYZ1.pyz/psycopg2.extras",
>  line 88, in execute
> IntegrityError: new row for relation "substance_intake" violates check 
> constraint "discontinued_after_started"

by not allowing that.

Actually, GNUmed is intended to check for this problem
before allowing a safe but their just might be a bug in
that. Unfortunately, however, Windows is so busy
reference-counting wxBegin/EndBusyCursor() calls that it is
unable to tell us about important problems.

Hence, can you describe exactly what you did so we can
reproduce this problem and fix it ?

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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