[Top][All Lists]

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

Re: [Gnumed-devel] What to do with information in popups

From: Ian Haywood
Subject: Re: [Gnumed-devel] What to do with information in popups
Date: Wed, 10 Nov 2004 14:33:52 +1100

On Tue, 9 Nov 2004 22:53:34 +0100
Karsten Hilbert <address@hidden> wrote:

> Unless, of course, you intend to *improve* upon the written
> record by allowing for data in limbo.

My inital plan would be to hold popup results in RAM until the SOAP
itself is committed, as it makes little sense to commit the popups
before committing the SOAP data.  The other alternative
is to have an "auto-save" timer to regularly commit the narrative so far
to the backend, as well as when popups are saved and when the user explicit 
requests a save.

Problem is, if the don't auto-save, in what form should this epheremal data be? 
cClinItem descendants
are the logical choice, but at present they can't exist before a backend row is 
 created. In this case, can we have an cClinItem.__init__ () option to create a 
empty "RAM-only" clinical object, then () creates the row?

PGP public key E750652E at
9BF0 67B7 F84F F7EE 0C42  C063 28FC BC52 E750 652E

Attachment: pgpHCaZK_wHWt.pgp
Description: PGP signature

reply via email to

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