[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] layout managers
From: |
Horst Herb |
Subject: |
Re: [Gnumed-devel] layout managers |
Date: |
Sun, 25 Jul 2004 23:50:20 +1000 |
User-agent: |
KMail/1.6.2 |
On Sun, 25 Jul 2004 23:32, Karsten Hilbert wrote:
> - table trigger sends NOTIFY with patient ID attached
> - no one emits NOTIFIES
The bit where this fails over is that NOTIFY cannot carry any parameters - at
least not tile version 7.3, and I doubt this has changed.
Thus, the backend can send a NOTIFY that *a* patient has changed, but that
mechanism won't tell you which one.
What you can do is construct a NOTIFY_PATID_1234 notice,
and whenever you intend to modify patient id 1234, you temporarily listen to
exactly that message - but it somehow generates more backend traffic rather
than saving it.
Hence, you can either lock a particular row as soon as you intend to edit it -
which will prevent anybody else to edit it at the same time - or it gets
very, very complicated.
That is, you'll have to do a "select for update" statement whenever you
consider the ere *possibility* that a user interface element will change
data.
Horst
- [Gnumed-devel] layout managers, Karsten Hilbert, 2004/07/24
- Re: [Gnumed-devel] layout managers, Ian Haywood, 2004/07/25
- Re: [Gnumed-devel] layout managers, Karsten Hilbert, 2004/07/25
- Re: [Gnumed-devel] layout managers, Karsten Hilbert, 2004/07/25
- Re: [Gnumed-devel] layout managers,
Horst Herb <=
- Re: [Gnumed-devel] layout managers, Karsten Hilbert, 2004/07/25
- Re: [Gnumed-devel] layout managers, Karsten Hilbert, 2004/07/25
- Re: [Gnumed-devel] layout managers, Karsten Hilbert, 2004/07/25