Here's a general question to developers : when resource tables are
missing sometimes odd things happen. The corrective action is always
the same - to generate the resource tables. Is there any sense in
automating this generation and, if so, what would be the sensible
trigger points:
1. on startup
2. as part of a scheduled task - eg right before or after datamart generation
···
On 27 June 2012 16:07, Kabango Malewezi <kmalewezi@jhpiego.net> wrote:
I agree this needs to be done, and has been discussed a number of
times. . There are numerous places in the system now where these
resource tables are required (data browser for instance). Trolling
back through the mailing list archives, one will see this issue coming
up a number of times, of various weird errors occuring because of the
lack of the tables. Not only do the resource tables need to be
present, but they need to be regenerated automatically, when certain
actions on the system occur, for instance, when a new orgunit is
added. When a new orgunit, data element, etc are added the tables are
out of sync with the rest of the metadata in the system. There is no
way to know that the system is "dirty" and that these resource tables
should be regenerated. So, we should have some mechanism of marking
these tables as dirty, and forcing a refresh each time (or at some
point maybe once an hour after they have been marked as dirty) such a
situation would occur. I am not opposed to automatic scheduling either
(probably each day before data mart) but I am not sure this would
really be good enough.
Regards,
Jason
···
On Wed, Jun 27, 2012 at 5:25 PM, Bob Jolliffe <bobjolliffe@gmail.com> wrote:
On 27 June 2012 16:07, Kabango Malewezi <kmalewezi@jhpiego.net> wrote:
It was exactly that. Thank you very much.
Good to hear.
Here's a general question to developers : when resource tables are
missing sometimes odd things happen. The corrective action is always
the same - to generate the resource tables. Is there any sense in
automating this generation and, if so, what would be the sensible
trigger points:
1. on startup
2. as part of a scheduled task - eg right before or after datamart generation