[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] GnuMed/Archive // patient object
From: |
Horst Herb |
Subject: |
Re: [Gnumed-devel] GnuMed/Archive // patient object |
Date: |
Mon, 20 Jan 2003 22:11:37 +1100 |
User-agent: |
KMail/1.4.3 |
On Mon, 20 Jan 2003 22:46, Thierry MICHEL wrote:
> Why not a layer which could map objects "transparently" to the database.
> The advantage is that in this case you handle *only* objects, finished
> with cursor and selects, insert and so on.
That's thee layer I am working on. Check the source of gmPgObject.py in the
CVS tree. There are still unresolved conceptual problems on how to resolve
many-to-many relationships best.
Horst
- [Gnumed-devel] GnuMed/Archive // patient object, Karsten Hilbert, 2003/01/19
- Re: [Gnumed-devel] GnuMed/Archive // patient object, Horst Herb, 2003/01/19
- Re: [Gnumed-devel] GnuMed/Archive // patient object, Ian Haywood, 2003/01/20
- Re: [Gnumed-devel] GnuMed/Archive // patient object, Karsten Hilbert, 2003/01/20
- Re: [Gnumed-devel] GnuMed/Archive // patient object, Karsten Hilbert, 2003/01/20
- Re: [Gnumed-devel] GnuMed/Archive // patient object, Horst Herb, 2003/01/20
- Re: [Gnumed-devel] GnuMed/Archive // patient object, Karsten Hilbert, 2003/01/20
- Re: [Gnumed-devel] GnuMed/Archive // patient object, Karsten Hilbert, 2003/01/20
Re: [Gnumed-devel] GnuMed/Archive // patient object, Karsten Hilbert, 2003/01/30