[Top][All Lists]

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

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

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Lab import - access to the database and logging
Date: Mon, 7 Nov 2011 20:09:38 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Mon, Nov 07, 2011 at 06:37:35PM +0000, Jim Busser wrote:

> >> 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)?

Sure, why not ?

> 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?

It needn't but it can. It doesn't matter. If I were to
decide I wouldn't make it so.

> 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.

It doesn't. That's what the default is for.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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