Re: [Gnumed-devel] Concurrent connections on the same patient

[Karsten Hilbert]

On Wed, Jun 27, 2012 at 10:09:49PM +0000, Jim Busser wrote:

> On 2012-06-27, at 1:33 PM, Karsten Hilbert wrote:
> 
> > Exactly. Due to the nature of things (concurrent work) the
> > exact order and timestamps may be somewhat different between
> > databases.
> 
> I do not imagine that it will often happen that a single patient (the same 
> patient) will have their record worked on simultaneously in two different 
> replications.

With respect to the order it does not matter whether people
work on the same patient.

However, I think it is correct to assume that the *relative*
order of changes to one patient will be identical IF said
one patient is only worked on by one person at a time.

> It raises in my mind the question of whether it may be
> useful to signal, to any user of an instance of GNUmed,
> whether the currently "activated" patient is
> 
> (a) having, at the same time, one or more read-only connections from one or 
> more other users and
> (b) being written-to by one or more other users and
> (c) perhaps who are the other users working at the same time on this patient
>       (because maybe some conversation among these staff could be
>       helpful to the patient)

This is not possible to know (because there are no locks).

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