Hi Jason, I see the problem. Analytics after 2.14 should remove all empty analytics tables though so you should not have all those empty tables between 0 and now.
Unless someone plans to use DHIS for archaeological research / studies of the ancient Greeks we could maybe hard code some sensible limits to protect from those extreme cases. Lars On Thu, Jun 12, 2014 at 1:45 PM, Jason Pickering < jason.p.picker...@gmail.com> wrote: > This may have been brought up before, but we get some data sometimes, > submitted in faraway time periods (like 1-1-0001). No clue really how this > gets in there, but it exposes a weakness in the analytics, in that if data > exists from these ancient (or far in the future time periods), many > thousands of tables will be created (since a table will be created for each > year, based on the minimum and maximum period). > > I would like to suggest that we implement a mechanism (perhaps a system > setting) to restrict the analytics to certain time ranges, namely > > 1) Ignore data for the analytics before... > 2) Igonore data for the analytics after.... > > Regards, > Jason > > > _______________________________________________ > 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 > >
_______________________________________________ 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
