Re: [Gnumed-devel] Identifying the current revision of the GNUmed database (was Country zones and i18n)

[Karsten Hilbert]

On Mon, Nov 28, 2011 at 04:00:54PM +0000, Jim Busser wrote:

> >>    gnumed_v16=> select * from gm.schema_revision where position('v16' in 
> >> filename) = 1 and position('fixup' in filename) > 0 order by pk ;
> >> 
> >> pk  |               filename                | version |           imported 
> >>            
> >> -----+---------------------------------------+---------+-------------------------------
> >> 585 | v16-clin-v_narrative4search-fixup.sql | 16.1    | 2011-11-26 
> >> 16:16:04.580231-08
> >> 586 | v16-cfg-report_query-fixup.sql        | 16.1    | 2011-11-26 
> >> 16:16:05.023574-08
> >> 587 | v16-i18n-fixup.sql                    | 16.4    | 2011-11-26 
> >> 16:16:05.423471-08
> >> 588 | v16-blobs-doc_desc-fixup.sql          | 16.5    | 2011-11-26 
> >> 16:16:05.869795-08
> > 
> > In a way, yes, except that you shouldn't get too involved
> > with the .version column. It may be wrong, it may have a
> > different format.
> > 
> > I would look out for the actual filename that I need to have
> > installed instead.
> 
> I am not sure how tech support would know what name they
> are looking for except

Whoever would prepare a data pack would (need to) know of
certain fixup files having to have been applied to a given
database in order for the data pack to succeed - in most
cases this will be none.

The data pack would check for those files and error out if
they cannot be found.

> I was just thinking it could be helpful for IT to check the state of how far 
> a database has been updated.

1) determine the major version

2) ./fixup_db.sh <determined major version>

3) be done with it

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