[Top][All Lists]

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

Re: [Gnumed-bugs] <bug>: neuen Kontakt anlegen

From: Karsten Hilbert
Subject: Re: [Gnumed-bugs] <bug>: neuen Kontakt anlegen
Date: Sat, 6 Feb 2016 17:32:43 +0100
User-agent: Mutt/1.5.24 (2015-08-30)

> system account: Martin

Hi Martin,

thanks for taking the time to report the problem

> 2016-02-04 12:40:03  ERROR     gm.person 
> (d:\workplace\gnumed-client.1.5.4\build\pyi.win32\gnumed\outpyz1.pyz\logging::exception()
>  #1088): error changing active patient to [[cPatient:188]: ['comment: NULL', 
> 'pk_emergency_contact: NULL', 'pk_identity: >>188<<', 'pk_primary_provider: 
> NULL', 'dob_is_estimated: >>False<<', 'emergency_contact: NULL', 'title: 
> NULL', 'xmin_identity: >>39433<<', 'tob: NULL', 'pk_marital_status: NULL', 
> 'pk_active_name: >>533<<', 'dob_only: >>1990-06-25 10:11:11.111000+01:00<<', 
> u'preferred: >>jd<<', u'firstnames: >>John<<', 'dob: >>1990-06-25 
> 10:11:11.111000+01:00<<', u'gender: >>m<<', u'marital_status: >>unknown<<', 
> u'l10n_marital_status: >>unknown<<', u'l10n_gender: >>m<<', 'cob: NULL', 
> u'lastnames: >>Doe<<', 'pupic: NULL', 'deceased: NULL']]
> Traceback (most recent call last):
>   File 
> "D:\workplace\gnumed-client.1.5.4\build\pyi.win32\gnumed\outPYZ1.pyz\",
>  line 2119, in set_active_patient
>   File 
> "D:\workplace\gnumed-client.1.5.4\build\pyi.win32\gnumed\outPYZ1.pyz\",
>  line 1887, in __init__
>   File 
> "D:\workplace\gnumed-client.1.5.4\build\pyi.win32\gnumed\outPYZ1.pyz\",
>  line 1759, in get_emr
>   File 
> "D:\workplace\gnumed-client.1.5.4\build\pyi.win32\gnumed\outPYZ1.pyz\Gnumed.wxpython.gmChartPullingWidgets",
>  line 189, in pull_chart
>   File 
> "D:\workplace\gnumed-client.1.5.4\build\pyi.win32\gnumed\outPYZ1.pyz\",
>  line 509, in _set_is_patient
>   File 
> "D:\workplace\gnumed-client.1.5.4\build\pyi.win32\gnumed\outPYZ1.pyz\",
>  line 1649, in turn_identity_into_patient
>   File 
> "D:\workplace\gnumed-client.1.5.4\build\pyi.win32\gnumed\outPYZ1.pyz\Gnumed.pycommon.gmPG2",
>  line 1445, in run_rw_queries
>   File 
> "D:\workplace\gnumed-client.1.5.4\build\pyi.win32\gnumed\outPYZ1.pyz\psycopg2.extras",
>  line 120, in execute
> IntegrityError: insert or update on table "patient" violates foreign key 
> constraint "fk_clin_patient_fk_identity"
> DETAIL:  Key (fk_identity)=(188) is not present in table "identity".

which you encountered while entering a new person into the database.

> user comment  : neuen Kontakt anlegen

You are running

> client version: 1.5.4

for which there's been 6 bug fix releases. Indeed, a fix for
the problem you report had been committed for version 1.5.7:

 commit e3b3d93963218d0ea06d2c203ced9d6518c36c42
 Author: Karsten Hilbert <address@hidden>
 Date:   Mon Aug 10 12:31:00 2015 +0200

    Fix patient change encounter signal exception

        The cClinicalRecord instance listens for clin.encounter
        modification signals from the database because it keeps a
        cached copy of the current encounter. However, it failed
        to only concern itself with modification signals actually
        pertaining to the cached encounter (rather than any
        encounter). Thusly, when another client changed any other
        encounter GNUmed would think it detected a modification
        to the current encounter and check for pending local
        changes. Now, most often there won't be any. Sometimes,
        however, there are, in which case GNUmed would blow up
        thinking it had detected a semantic concurrency
        violation. Make GNUmed now check the encounter that's
        reported to be modified. Reported by Marc.

Unfortunately, we don't yet offer upgraded Windows packages
but you can still run the source release on Windows if you
have Python etc installed.

It would be good to know whether the latest release fixes the
problem for you.

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]