[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] further testing / bugs

From: Hilmar Berger
Subject: Re: [Gnumed-devel] further testing / bugs
Date: Wed, 10 Aug 2005 09:24:22 +0200

On Tue, 9 Aug 2005 21:11:16 +0200
Karsten Hilbert <address@hidden> wrote:

> On Tue, Aug 09, 2005 at 08:47:45PM +0200, Hilmar Berger wrote:
> > If this is true, why line A gets executed in the very moment that 
> > get_episodes called by line B (from EMR tree widget) ???
> If you are saying that calling get_episodes() somehow
> *triggers* a call to _db_callback_episodes_modified()
> then I don't know why. If that's not what you are saying
> I don't understand what you are saying.

If I remember well, the problem in get_episodes was that the callback (line A) 
deleted self.__db_cache['episodes'] while trying to update the episodes in 
__db_cache (that should have be called from EMR-tree which was triggered by 
line B.
To me it looked like line A was executed in the very moment the ro_query was 
done. If I find time, I will look if this is still true. 
If true it would mean that either

DB = signal-middleware
(i.e. line A was executed after line B, which sounds too strange to be true)

or that two signals were send, the first triggering the frontend update while 
the second somehow only triggered the deletion of self.__db_cache['episodes']. 
I remember that there was exactly one call to get_episodes after adding a 
health issue to a new patient (=my bug triggering condition). 

Well, I guess I will have to test it again :).



reply via email to

[Prev in Thread] Current Thread [Next in Thread]