Re: [Gnumed-devel] Gnumed Value Objects dev guide, draft 1

[Ian Haywood]

On Fri, 16 Apr 2004 20:11:38 +0200
Carlos Moro <address@hidden> wrote:

>       - Each instance verifies its existence upon instantiation.
I'm still worried this is going to get slow, especially when returning long 
lists of VOs.
Better to have a single query which grabs a list of object PKs *and* fields to 
instantiate VOs en bloc.

>       - Creation of new entries in the database is NOT supported
I assume instead there are factory methods on gmClinicalRecord for each VO 
class.
gmClinicalRecord could end up rather large in this case. 
Would it be better to let VO classes have a constructor which takes the 
gmClinicalRecord of the current
patient as a parameter, if only to distribute code around files a bit more.

>       _cmds_store_payload: It's important to perform row locking before 
> writting operation.
Why is this? commits are isolated from each other on postgres anyway.   
        
>       cVaccination: Done
>       cLabRequest: Done
>       cLabResult: Done
>       cAllergy: Done
Wow, good work.

Thanks for writing this doc

Ian

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

pgpKWuSBuocYS.pgp
Description: PGP signature