Re: [Gnumed-bugs] 1.0.rc5 release

[Karsten Hilbert]

On Thu, Oct 06, 2011 at 10:35:07AM -0700, Jim Busser wrote:

> 1) shall I 
> 
>       update ref.data_source
>       set pk=9
>       where pk=10

Given this:

>       select pk_audit, pk, name_short, version,
>       row_version, modified_when, modified_by
>       from ref.data_source where pk > 7 ;
> 
> gnumed_v15->
> 
>  pk_audit | pk | name_short |    version    | row_version |         
> modified_when         | modified_by 
> ----------+----+------------+---------------+-------------+-------------------------------+-------------
>     13331 |  8 | FreeDiams  | 0.5.4         |           0 | 2011-05-05 
> 14:39:50.368841-07 | any-doc
>     13891 | 10 | LOINC      | 2.26          |           0 | 2011-07-28 
> 08:13:24.483741-07 | any-doc

Yes, indeed, the above will help *in your case*.

Assuming thet repeated runs of "Update LOINC" would
delete/re-insert the LOINC row (thusly advancing the PK)
I'll have to devise another more general method to apply in
the database upgrade SQL scripts.

Same with ATC ref.data_source.pk for that matter (despite
not yet being observed in the field).

> 2) Should
> 
>       Update LOINC
> 
> menu option (and code) be pulled out of client v1 and instead deployed as a 
> data pack?

Yes, indeed. Once we've got a data pack we can easily
deactivate the option - which is OK doing within any
1.x.y maintenance release even.

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