Re: [Gnumed-bugs] Managing encounter types: renaming Local name *back* to Encounter name is refused

[Busser, James]

FWIW the only human error encountered when I was manually altering my backend 
data was the following which resulted from a copy / paste (which should not 
have included a copy of the psql prompt)

        gnumed_v16=> begin ;
        BEGIN
        gnumed_v16=> update clin.encounter_type
        gnumed_v16-> gnumed_v16-> set description = 'seen in clinic' where 
description = 'in surgery' ;
        ERROR:  syntax error at or near "->"
        LINE 2: gnumed_v16-> set description = 'seen in clinic' where descri...
                          ^
        gnumed_v16=> update clin.encounter_type set description = 'seen in 
clinic' where description = 'in surgery' ;
        ERROR:  current transaction is aborted, commands ignored until end of 
transaction block
        gnumed_v16=> rollback

however it is likely irrelevant, in view of the abortion and my subsequent 
rollback.

Also, I checked my database fingerprint by rerunning (from the downloaded 
[...]/server/ directory)

        ./gm-fingerprint_db.py gnumed_v16 gm-dbo

and it remains the same as what I emailed Sebastian (from before my hacking) :

        0bcf44ca22c479b52976e5eda1de8161

therefore GNUmed client must be objecting to a change that I made in the data?

-- Jim