Re: [Gnumed-devel] "reference"/"enum" tables outside "ref" schema

[Karsten Hilbert]

> In order to get rid of test data I tried to backup and restore database
> schema, and then selectively restore configuration data and required
> lists. (Is there any script to do this?)

Unfortunately not.

> It was more complicated than I thought, because some useful lists were
> in "clin" and "dem" schemas.

I know :-(

> Below are the tables I had to include
> (besides all in "cfg" and "ref" schemas):
> 
> clin.encounter_type
> clin._enum_allergy_type
> clin.fhx_relation_type
> dem.country
> dem.enum_comm_types
> dem.gender_label
> dem.inbox_item_category
> dem.inbox_item_type
> dem.marital_status
> dem.name_gender_map
> dem.relation_types
> dem.state
> 
> All these tables actually contain config data.

In a way, yes.

I will look at them in more detail and likely move some of
them. Thanks for the hint.

> Also in "gm" schema there is "access_log" table, which should be empty
> in new installation

It should only be empty when it is emptied out by the local
admin. GNUmed has no say in when that is appropriate.

> but there are gm.notifying_tables and
> gm.schema_revision tables, which should contain data. Why not move
> "access_log" to "audit" schema?

Not a bad suggestion !

Karsten