Re: [Gnumed-devel] Re-bootstraping problem & fring around with the conf-file

[Karsten Hilbert]

> When re-bootstrapping I got the following error:

> Things worked after I added 'sql/gmAudit.sql' to the schema in my
> conf-file.
Ah, thanks for reminding me. I nearly forgot.

> postgres version = 7.1
> registration database = core
> schema = $schema$
> sql/gmAudit.sql
> sql/gmidentity.sql

Actually, gmAudit.sql belongs into the database level schema
as it is needed for any GnuMed database independant of the
service. I will update the conf files accordingly.

Also note that gmI18N and gmSchemaRevision are now handled
more cleanly by not including them in every service level sql
file but importing them at database schema level. This change
does not break things because we did explicitely import them
with the first service already and all services reside in one
database, incidentally.

> I reckon their following might need some revision:
> bootstrap-standard-AU.conf
> bootstrap-standard-DE.conf
> bootstrap-standard.conf.template
Yes.

> Changes have to made in:
> gmclinical.sql
No.

> I imagine the question here is:
> Is auditing going to be standard?
I feel: Yes. I'm sure Horst will agree (which does not
necessarly mean he will agree to the current scheme of
going about things auditing).

So, the lesson here is that when people want to re-bootstrap
they need to remake their conf file from the standard ones.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346