https://blueprints.launchpad.net/dhis2/+spec/zerovalue-trigger
I am thinking if it makes any sense in the current context of DHIS2 to store zero values. Maybe we should intercept them (sort of like a DB trigger) and put them some place else if people actually care about them. Should increase performance. Of course, we currently have a maintainence function to delete the values, but it might be nice to intercept them at the point of data entry/import and put them some place else. A system setting could be used in order to allow people to choose where zero values should be handled like 1) never record them anywhere 2) record them in datavalue table 3) record them in datavalue_zeros table. Just a wacky idea early in the morning, but might be useful. Regards, Jason -- Jason P. Pickering email: [email protected] tel:+260968395190 _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
