|
From: | James Busser |
Subject: | Re: [Gnumed-devel] GNUmed Release 0.3.4 |
Date: | Tue, 28 Oct 2008 07:51:44 -0700 |
On 28-Oct-08, at 4:42 AM, Karsten Hilbert wrote:
0.3.4 ... fixed only one problem: The failure to properly set the database language on startup.
Database: 1) if you are running a gnumed_v9 database already - download the v9 server tarball - go to server/sql/v8-v9/fixups/ - edit v9-i18n-dynamic.sql:- remove the "--" before "set default_transaction_read_only to off"- run the script like this: psql -d gnumed_v9 -U gm-dbo -f v9-i18n-dynamic.sql (you can safely repeat this procedure any number of times)
Just wondering how the above client depends on any existing v9 database to get "changed" and why a freshly-created v9 would not need the same thing to be done.
Is the dependency or problem outside of the bootstrapper? IOW, was it the pre-0.3.4 clients which had "done something " to existing v9 databases? The bootstrapper is therefore unchanged, and client 0.3.4+ will avoid committing the problem, but any affected (already-touched- by-pre-0.3.4) v9 needs to be manually fixed using the psql script?
[Prev in Thread] | Current Thread | [Next in Thread] |