Re: [Gnumed-bugs] [Gnumed-devel] 1.0.rc5 release

[Jim Busser]

On 2011-10-06, at 2:50 PM, Karsten Hilbert wrote:

> I suppose your suspicion is correct. Now, looking at
> 
>       client/business/gmLoinc.py::loinc_import()
> 
> confirms at least the possibility of the above being the reason.

After setting pk=10 to pk=9, I can now not update because I lack pk=10.

I cannot clone the pk=9 record into a pk=10 because they cannot share the same

        version, name_long

which I could get around by faking a version 2.261 but that may leave trapped 
other individuals who might be in the same situation in

        GNUmed client 0.9x, database v15

if they too, like me, had re-run LOINC updater.

Maybe all records in anybody's v15 production, and which use LOINC version 
2.26, need to be resolved and re-keyed so as to reference a single row in 
ref.data_source, so that the other one can be deleted and no longer required in 
the v15 v16 update in case anybody other than myself had run the LOINC updater 
in client 0.9x

??

-- Jim