[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 3, Issue 29
From: |
Hilmar Berger |
Subject: |
Re: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 3, Issue 29 |
Date: |
Mon, 24 Feb 2003 23:43:57 +0100 (CET) |
On Mon, 24 Feb 2003, Karsten Hilbert wrote:
> > For instance, is it at each page viewing change? What if there are 2
> > clinicians entering data and the scope of the transaction boundary is
> > patient wide, so that one clinician finishes his entry and then is
> > informed his update is aborted because MVCC detects that there is a
> > read-write write-read or write-write conflict.
> His update isn't aborted but displayed for merging.
I agree that this will work well for text-only entries. It might prove
difficult to display differences for non-text data. BTW, how would
gnumed-archive handle this problem when picture/sound/whatever data are
concerned ?
Hilmar
- [Gnumed-devel] Re: Gnumed-devel Digest, Vol 3, Issue 29, sjtan, 2003/02/24
- Re: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 3, Issue 29, Karsten Hilbert, 2003/02/24
- Re: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 3, Issue 29, Karsten Hilbert, 2003/02/24
- Re: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 3, Issue 29, Horst Herb, 2003/02/24
- Re: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 3, Issue 29,
Hilmar Berger <=
- Re: [Gnumed-devel] Re: Gnumed-devel Digest, Vol 3, Issue 29, Horst Herb, 2003/02/24