[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] release 0.4.4

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] release 0.4.4
Date: Fri, 8 May 2009 23:52:46 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Fri, May 08, 2009 at 04:27:33PM -0300, Rogerio Luz wrote:

> How do I update my v10.0 DB to v 10.4 ??

There is no need for a "real" update as would be needed
from, say, v10 to v11. Nonetheless, there are so far three
SQL-level fixes:

        FIX: SQL: delete_document: .date is now .clin_when
        FIX: SQL: clin.v_pat_allergy_state_journal missed data due to 
unintended use of coalesce()
        FIX: SQL: fix sync of clin.allergy_state with clin.allergy on saving 
the first allergy for a patient

which are good to have. They can be applied by hand to your
existing database. The process can be re-run as often as
needed. It works like this:

- log into your database machine

- make sure you can connect to "gnumed_v10" as "gm-dbo"

        test: $> psql -d gnumed_v10 -U gm-dbo

- go to the server/sql/v9-v10/fixups/ directory

- in each file change the line

        "--set default_transaction_read_only to off;"


        "set default_transaction_read_only to off;"

                (IOW, remove the "--")

- run the following command on each file:

        $> psql -d gnumed_v10 -U gm-dbo -f <FILENAME>

- note that "v10-clin-v_emr_journal-fixup.sql" MUST
  be the run last

GNUmed 0.5 already has a shell script making it easy to
apply such fixups.


While this process doesn't really have the potential to do
anything adverse to your data it is ALWAYS a good idea to
have a RECENT BACKUP available.

Feel free to improve

(way down at the bottom ;-)

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]