Re: [Gnumed-devel] Lab import - access to the database and logging

[Busser, Jim]

On 2011-11-06, at 12:40 PM, Karsten Hilbert wrote:

>> A configuration file is shaping up to have
>> 
>> [db]
>> host = localhost
>> port = 5432
>> dbname = gnumed_v16
>> user = 
>> password = 
>> 
>> [logging]
>> lg_user = 
>> lg_pwd = 
>> lg_file_path = 
>> 
>> 
>> For access to write into the database, should the user be
>> 
>> - separate from gm-dbo ?
> 
> Most definitely.
> 
>> - created not as a staff via GNUmed but via (e.g.) psql or python script?
> 
> If you use a dedicated database accoung which you do not
> intend to use as a staff login you can forgo linking a name
> and staff record to it.

Might I suggest

        gm-dbi

where the 'i' stands for 'importer' and leaving to a later time whether there 
should exist any more highly-constrained importers for specific purposes (like 
lab vs other)?

Also, that the same way that

        gm-dbo

does not appear among the staff users, the above-proposed gm-dbi should 
likewise not exist listed in the staff table?


Lastly a number of tables have a default

        Col name        TYPE    Description
        modified_by     name    NOT NULL DEFAULT "current_user"()

and so I wondered in the case of a script that would create new records (python 
lab importer) how it references the name (say 'gm-dbi') that is to be written 
into the rows. Would the python script use the literal value 'gm-dbi' or would 
the script reference some property of the current connection login which would 
be resolvable to

        gm-dbi

??

-- Jim