Great. On Wed, Nov 19, 2014 at 10:01 AM, Mahendra Kariya < [email protected]> wrote:
> We will take care of this when we deploy 2.17. > > Thanks! > > On Wed, Nov 19, 2014 at 1:36 PM, Lars Helge Øverland <[email protected]> > wrote: > >> Hi Mahendra, >> >> there is nothing you must do, as the field is nullable. >> >> There isn't really a scripted upgrade path, since the field is unique and >> max 50 char. However you can try this SQL: >> >> update dataelementcategoryoption set name = substring(name,0,50); >> >> In 2.17 we have a new option for display either name or short name in >> analysis apps, and hence it could be good to set this. >> >> regards, >> >> Lars >> >> >> >> >> On Wed, Nov 19, 2014 at 5:10 AM, Mahendra Kariya < >> [email protected]> wrote: >> >>> Hi Lars, >>> >>> We just noticed that a new mandatory field 'shortName' has been added to >>> category options. >>> >>> We were just wondering about the migration strategy for the data which >>> is already in prod without the short name. Do we need to do something about >>> it or DHIS will take care of this scenario internally? >>> >>> >>> >>> Thanks, >>> Mahendra >>> >> >> >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
