[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] re allergy signalling
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-devel] re allergy signalling |
Date: |
Wed, 19 Nov 2003 23:29:15 +0100 |
User-agent: |
Mutt/1.3.22.1i |
>> gmAllergies in business/ should not ever have to send a
>> intra-client signal "allergy_updated". The clinical record
>> object should catch the database insertion/update/delete,
>> invalidate it's cache and notify the GUI code via that signal.
>>
>> The top panel does listen for that signal.
> How?
> Is this done via postgres notify /listen ?
Yes and no. gmClinicalRecord listens to postgres notifies
regarding the allergies table. Upon reception it invalidates
its cache and notifies the frontend via intra-client signals
through gmDispatcher. Or so it is intended to work. If it
doesn't it's a bug.
Oh, and the allergies table insert/update/delete notify
trigger is currently hardcoded but I am thinking of
auto-generating them from within bootstrap*
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346