[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-bugs] [Gnumed-devel] 1.0.rc5 release
From: |
Jim Busser |
Subject: |
Re: [Gnumed-bugs] [Gnumed-devel] 1.0.rc5 release |
Date: |
Thu, 06 Oct 2011 19:36:27 -0700 |
On 2011-10-06, at 6:19 PM, Jim Busser wrote:
> 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
Resolving the constraints against duplication, by assigning a 'sham' version,
worked:
from shell:
./psql -d gnumed_v15 -U gm-dbo
then
set default_transaction_read_only to off;
update ref.data_source
set pk=10 where pk=9 ;
\copy (select* from ref.data_source where pk=9) to '~/temp.sql'
update ref.data_source
set pk=9 where pk=10 ;
update ref.data_source
set version=2.259 where version=2.26 and pk=9
\copy ref.data_source from '~/temp.sql'
then from
/Users/djb/Downloads/gnumed-server.16.rc5/server/bootstrap
sh upgrade-db.sh 15 16
…
==> dropping pre-existing target database [gnumed_v16] ...
==> cloning [gnumed_v15] (111 MB) as target database [gnumed_v16] ...
==> transferring users ...
==> bootstrapping "v15-v16-static" ...
==> bootstrapping "v15-v16-dynamic" ...
==> setting up auditing ...
==> setting up notifications ...
==> upgrading reference data sets ...
==> verifying target database schema ...
==> checking migrated data for plausibility ...
Done bootstrapping GNUmed database: We very likely succeeded.
Message not available