> Short term, since I have no option currently except getting down and dirty > in the sql to workaround, I guess I should instead create a new table for > updated orgunit ids, but whose update stamp takes into account groups, > attributes and what have you. And leave the orgUnit lastUpdated untouched. > > There might be a secondary benefit of having a separate table for logging > orgunit updates via trigger .. I could possibly also record the deletions > which is currently another missing functionality in the picture. Hopefully > will get time to look more at this tomorrow. > > Okay. Could another temporary work-around be to just check for recent updates of org unit groups through the web api?
_______________________________________________ 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
