Re: [Gnumed-devel] database replication with bucardo

[Karsten Hilbert]

On Fri, Aug 17, 2012 at 03:10:41PM +0200, Slappinjohn wrote:

> to sum it up --- bucardo sucks. Got it working, but multiple errors
> occured in 2nd db (patient with number xxx not found, etc. - log appended)

...

> 2012-07-08 12:49:51  ERROR     gm.db 
> (/usr/share/gnumed/Gnumed/pycommon/gmPG2.py::run_rw_queries() #1262): error 
> running RW query
> Traceback (most recent call last):
>   File "/usr/share/gnumed/Gnumed/pycommon/gmPG2.py", line 1260, in 
> run_rw_queries
>     curs.execute(query['cmd'], args)
>   File "/usr/lib/python2.7/dist-packages/psycopg2/extras.py", line 123, in 
> execute
>     return _cursor.execute(self, query, vars)
> IntegrityError: duplicate key value violates unique constraint 
> "access_log_pkey"
> DETAIL:  Key (pk)=(3047) already exists.
> KONTEXT:  SQL statement "insert into gm.access_log (user_action) values ('EMR 
> access: ' || _action)"
> PL/pgSQL function "log_access2emr" line 8 at SQL statement

Did the table "gm.access_log" and the sequence
"gm.access_log_pk_seq" get replicated ?

> 2012-07-08 12:49:51  ERROR     gm.person 
> (/usr/share/gnumed/Gnumed/business/gmPerson.py::set_active_patient() #1572): 
> error changing active patient to [[cIdentity:424]: [u'comment: NULL', 
> u'pk_emergency_contact: NULL', 'pk_identity: >>424<<', u'pk_primary_provider: 
> NULL', u'karyotype: NULL', u'emergency_contact: NULL', u'title: NULL', 
> u'l10n_marital_status: >>unbekannt<<', u'tob: NULL', u'pk_marital_status: 
> NULL', 'pk_active_name: >>440<<', 'dob_only: >>1943-10-10 
> 11:11:11.111000+01:00<<', u'preferred: NULL', u'firstnames: >>Karin<<', 'dob: 
> >>1943-10-10 11:11:11.111000+01:00<<', u'gender: >>f<<', u'marital_status: 
> >>unknown<<', 'xmin_identity: >>74341<<', u'l10n_gender: >>w<<', u'cob: 
> NULL', u'lastnames: >>Gro\xdfmann<<', u'pupic: NULL', u'deceased: NULL']]

... this is just a followup error ...

> IntegrityError: duplicate key value violates unique constraint 
> "access_log_pkey"
> DETAIL:  Key (pk)=(3047) already exists.
> KONTEXT:  SQL statement "insert into gm.access_log (user_action) values ('EMR 
> access: ' || _action)"
> PL/pgSQL function "log_access2emr" line 8 at SQL statement

...

> 2012-07-08 12:49:59  ERROR     gm.person 
> (/usr/share/gnumed/Gnumed/business/gmPerson.py::__run_pre_selection_callbacks()
>  #1436): callback [<bound method gmTopLevelFrame._pre_selection_callback of 
> <Gnumed.wxpython.gmGuiMain.gmTopLevelFrame; proxy of <Swig Object of type 
> 'wxFrame *' at 0x3a14d10> >>] failed
> Traceback (most recent call last):
>   File "/usr/share/gnumed/Gnumed/business/gmPerson.py", line 1434, in 
> __run_pre_selection_callbacks
>     successful = call_back()
>   File "/usr/share/gnumed/Gnumed/wxpython/gmGuiMain.py", line 991, in 
> _pre_selection_callback
>     return self.__sanity_check_encounter()
>   File "/usr/share/gnumed/Gnumed/wxpython/gmGuiMain.py", line 1012, in 
> __sanity_check_encounter
>     emr = pat.get_emr()
>   File "/usr/share/gnumed/Gnumed/business/gmPerson.py", line 1288, in get_emr
>     raise AttributeError('cannot access EMR')
> AttributeError: cannot access EMR

As well as this. Which leads to the patient not being
activated properly.

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