gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] Country zones and i18n


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Country zones and i18n
Date: Tue, 15 Nov 2011 11:46:33 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Mon, Nov 14, 2011 at 10:36:10PM +0000, Jim Busser wrote:

> 1) when issuing an sql command like
> 
>       insert into dem.state (code, country, name) values ('AB', 'CA', 
> i18n.i18n('Alberta')); 
> 
>       --> does the i18n.i18n establish an original 
> 'able-to-be-translated-term' despite that
>               no actual translation might be offered until some later time?

Yes.

> 2) following the recreation of Canadian provinces I issued
> 
>       select dem.gm_upd_default_states();
> 
> but when I tried to issue
> 
>       -- do simple revision tracking
>       delete from gm_schema_revision where filename = '$RCSfile: 
> gmDemographics-Data.ca.sql,v $';
>       INSERT INTO gm_schema_revision (filename, version) VALUES('$RCSfile: 
> gmDemographics-Data.ca.sql,v $', '$Revision: 1.5 $');
> 
> I got
> 
>       ERROR: relation "gm_schema_revision" does not exist 
> 
> ?? is that obsolete (the Canadian sql was from 2006)

It is obsolete in the above form. The reason being, however,
that the SQL applies to a gnumed_v2 database rather than a
gnumed_v16 one. The time since 2006 does not play a role.
You could issue the above in a gnumed_v2 database 20 years
from now and expect it to suceed.

Care to turn the existing demographics into data packs ?  ;-)

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



reply via email to

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