[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] update database - no problem
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] update database - no problem |
Date: |
Tue, 9 Oct 2007 14:09:02 +0200 |
User-agent: |
Mutt/1.5.16 (2007-06-11) |
On Tue, Oct 09, 2007 at 11:50:20AM +0000, Syan Tan wrote:
> There was a post about trying to justify using xmin,
> which was something like "it isn't pretty enough".
Well, XMIN's pretty 'nuff for me at the moment. The thread
was mainly to let Dave (and the list archive) know that:
- yes we know XMIN can become a problem sometime later
- yes we know how to solve that
- yes we are open for patches to do so
> Actually, isn't having data cached at clients in database
> objects like having a replicated database when two or more
> clients have opened the same medical record.
multi-master, that is
> So if one
> could make it look pretty by implementing two-phase commit
> protocol amongst all the clients as well as the server.
That'd be possible but wouldn't exactly reduce complexity,
methinks ?
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- Re: [Gnumed-devel] update database - no problem, Karsten Hilbert, 2007/10/06
- Re: [Gnumed-devel] update database - no problem, Karsten Hilbert, 2007/10/06
- Re: [Gnumed-devel] update database - no problem, Karsten Hilbert, 2007/10/07
- Re: [Gnumed-devel] update database - no problem, Syan Tan, 2007/10/09
- Fwd: Re: [Gnumed-devel] update database - no problem, Syan Tan, 2007/10/09
- Re: Fwd: Re: [Gnumed-devel] update database - no problem, Syan Tan, 2007/10/09
- Re: [Gnumed-devel] update database - no problem, Syan Tan, 2007/10/09
- Re: [Gnumed-devel] update database - no problem,
Karsten Hilbert <=
- Fwd: Re: [Gnumed-devel] update database - no problem, Syan Tan, 2007/10/10
- Re: [Gnumed-devel] update database - no problem, Karsten Hilbert, 2007/10/10