Re: [Dhis2-devs] [Dhis2-users] Problem upgrading from 2.20 to 2.21

2016-07-22 Thread Bob Jolliffe
Thanks all. The startup routines should take care of all this stuff without the need for running manual queries. And indeed they do unless they fail - which as Dan says they do horribly when they do, I have deleted the offending views and everything started up fine. On 22 July 2016 at 14:33,

Re: [Dhis2-devs] [Dhis2-users] Problem upgrading from 2.20 to 2.21

2016-07-22 Thread Bob Jolliffe
Yes that does help. And the upgrade notes tell you to do this. Unfortunately when users create views directly through the database rather than through the application they need to be tracked down and removed. Fortunately all these were prefixed with _view so I could grab them all with 'pg_dump

Re: [Dhis2-devs] [Dhis2-users] Problem upgrading from 2.20 to 2.21

2016-07-22 Thread Michael Mwebaze
Hi Bob, Can you update the dataelement table on postgres by running an update query and setting the aggregationtype to 'SUM' where it is 'sum'? UPDATE dataelement set aggregationtype = 'SUM' where aggregationtype = 'sum'; Regards, Michael On 22 July 2016 at 09:09, Bob Jolliffe

Re: [Dhis2-devs] [Dhis2-users] Problem upgrading from 2.20 to 2.21

2016-07-22 Thread Timothy Harding
Unfortunately, I do not have a query that will quickly uppercase that column, but here is the mapping I used when doing my 2.20 -> 2.21 though: sum SUM average AVERAGE_SUM_ORG_UNIT avg AVERAGE count COUNT stddev STDDEV variance VARIANCE min MIN max MAX I'm surprised that somehow "average" was