Re: [Gnumed-bugs] Unhandled exception re-signing one measurement in multi-value cell

[Karsten Hilbert]

> In 1.3.7, in a cell containing 3 blood pressures from the same date, I had 
> signed
> 
> - two as normal, not relevant
> - one as abnormal, relevant
> 
> which caused all three to be displayed in red (which I think in future will 
> be shaded).
> 
> What I then did was to
> - double-click the cell
> - request to edit the value which had been signed as abnormal, relevant
> - in the edit box, I clicked "Sign" and unchecked abnormal and relevant
> 
> The exception seems to relate to a trigger and notification, lines 1572 - 
> 1576 which I will separately email
> 
> 2013-07-24 15:00:43  DEBUG     gm.logging 
> (/Users/djb/Downloads/gnumed-client.1.3.7/Gnumed/pycommon/gmLog2.py::log_stack_trace()
>  #170):               pg_exc = relation "dem.item_inbox_category" does not 
> exist
> LINE 1: ..._category, description ) values ( (select pk from dem.item_i...
>                                                              ^
> QUERY:  insert into dem.inbox_item_type ( fk_inbox_item_category, description 
> ) values ( (select pk from dem.item_inbox_category where description = 
> 'clinical'), 'results review change' )
> CONTEXT:  PL/pgSQL function "trf_notify_reviewer_of_review_change" line 28 at 
> SQL statement

A perfect example of what happens when one "just changes one part of the 
database schema".

Will fix.

Karsten