Hi Tran,
Thank you for sharing me the new requirements. Could you please also share the same to the rest of the group as well.
I have a question for your requirement number 5: changing data model !
You want to have an association between patientDataValue and Program. I don’t agree with this for two reasons
-
we already have a means to reach programs from patientdatavalue through programStageInstance
-
if we are to implement your new suggestion, we will have lots of duplications which will be against db normalization
I don’t think we are paying too much speed price with the current model.
Abyot.
Abyot,
my concern is only on how long it will take to generate any query if we have to link three table to get that patient and program enrollment. If the association is has no problem with the performance then we can remove it. Please give a try to populate the database and generate the query.
I guess the having a patient and program asscioation will make some increase in performance. if you think it dosent then we can remove it.
OK
···
On Fri, Oct 22, 2010 at 3:56 PM, Abyot Gizaw abyota@gmail.com wrote:
Hi Tran,
Thank you for sharing me the new requirements. Could you please also share the same to the rest of the group as well.
I have a question for your requirement number 5: changing data model !
You want to have an association between patientDataValue and Program. I don’t agree with this for two reasons
- we already have a means to reach programs from patientdatavalue through programStageInstance
- if we are to implement your new suggestion, we will have lots of duplications which will be against db normalization
I don’t think we are paying too much speed price with the current model.
Abyot.
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp