Re: [Gnumed-devel] re: create_identity

[Karsten Hilbert]

> I checked out gmPG. Doing the change below works to return the 
> identity's id.
Actually run_commit() is smarter. It checks the
cursor's description attribute to find out whether it makes
sense to fetch any rows. The DBAPI says that it is None if
there were no rows returned from the last query.

> But then when the patient_selected signal is sent, I get a list
> error which occurs in gmDemographicRecord.getActiveNames().
> This is understandable because only the identity is created ,
> but no names are.
Sure :-)    getActiveName() was missing a check for
if len(data) == 0 ...   It now returns a tuple of '**?**' for
first and last names if the query successfully returned no
data.

> That was another reason why just
> inserting into v_basic_person worked,
That's a better reason, actually.

> The error message is now:
> [PANIC] 
> (/home/sjtan/projects/gnumed/gnumed/client/business/gmPatient.py::__init__:216):
>  cannot connect with patient [8]
...
> [PANIC] 
> (/home/sjtan/projects/gnumed/gnumed/client/business/gmPatient.py::__init__:216):
>  IndexError: list index out of range<#10-0x0A-lf>

> Looking in gmDemographicRecord.getActiveName, we find the list which has 
> an index error is data ?  ( len of data is zero?) :
Yep. Fixed.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346