Re: [Gnumed-devel] Data packs

[Karsten Hilbert]

On Sun, Sep 25, 2011 at 01:00:28PM -0700, Jim Busser wrote:

> >> What I don't know is whether -- in the case of
> >> interruptions invoked from outside the script -- the
> >> transaction will remain "open" such that new activity in
> >> GNUmed will be lost on account of delayed failure of a
> >> commit.
> 
> I meant
> 
>       'delayed failure of a commit and therefore a rollback'

I understood as much.

> because… following an interruption in the data pack
> process, the connection eventually dies and any new activity
> issued from the originating client will be a new process
> inside a new connection?

It won't be a new process. If the new activity is read-only
it will re-use the per-thread read-only connection (which
does not matter because the data pack used a read-write
connection). If the new activity is read-write it will get a
whole new connection.

> In which case… what is it that allows new connections
> without re-providing the GNUmed userid and password

gmPG2.py

> (i.e. without re-autenticating) ?

It does re-authenticate with each new read-write connection.

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