dhis2-devs team mailing list archive

[Lars Helge Øverland <lars@xxxxxxxxx>]

Hi Chathura,

currently the approach to achieve this is to rely on the alphabetical
ordering of SQL view names. For the scheduled tasks, the system first drops
the SQL views in *reversed* alphabetical order. Finally, the system
regenerates the SQL views in alphabetical order.

So in your case where A depends on B, you should ensure that that the name
of SQL view B comes before the name of SQL view A alphabetically. This way,
the system will first drop A, then B, and when it is time to regenerate the
views, first generate B, then A, and you should be good.

best regards,

Lars

On Tue, Oct 4, 2016 at 11:10 AM, chathura widanage <
chathurawidanage@xxxxxxxxx> wrote:

> Dear Devs,
>
> We have two SQLViews created in DHIS2 v2.24 where one view depends on
> other one(Say, A depends on B). We have also scheduled an automatic
> maintenance event every day at 12.00 a.m. Problem is DHIS2 tries to drop
> view B first during this automated procedure and as a result whole
> procedure fails including analytics table generation.
>
> Is there a way to make DHIS2 scheduled event drop A before B in above case.
>
> Thanks & Regards,
> Chathura Widanage
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
lars@xxxxxxxxx
http://www.dhis2.org <https://www.dhis2.org/>