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: jason.p.pickering@gmail.com
tel:+260968395190
currently it works like this: We are not storing zeros for data elements with aggregation operator sum. We are storing zeros for data elements with aggregation operator average (since they are meaningful in aggregation). For each individual data element one can define whether zeros are significant or not (for special cases), which overrides the mentioned rules.
Making even more complex than this sounds like a bit too much to me…
I think you are probably right. It does become a bit too complex I
think for most use cases.
I will write up a short blurb at some point on how to do this with a
database trigger instead for those (probably absolutely no one) other
than me care about.
Will mark the blueprint as invalid as well.
···
2011/1/27 Lars Helge Øverland <larshelge@gmail.com>:
Hi,
currently it works like this: We are not storing zeros for data elements
with aggregation operator sum. We are storing zeros for data elements with
aggregation operator average (since they are meaningful in aggregation). For
each individual data element one can define whether zeros are significant or
not (for special cases), which overrides the mentioned rules.
Making even more complex than this sounds like a bit too much to me...
Lars
On Thu, Jan 27, 2011 at 9:07 AM, Jason Pickering > <jason.p.pickering@gmail.com> wrote:
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: jason.p.pickering@gmail.com
tel:+260968395190