dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi Jason,

yes it will be removed for 2.9.

My only concern for removing the constraint is that it is still unique
in the database mapping/application. So when the system queries by
data element alternative name during the import process and finds
multiple objects with the same alt name then an exception will be
thrown. Maybe dropping the constraint then nulling all alternative
names after import would be a solution.

Lars


On Mon, Jun 18, 2012 at 11:21 AM, Jason Pickering
<jason.p.pickering@xxxxxxxxx> wrote:
> It seems we have discussed this at length actually. I had forgotten
> about this thread.
>
> Is there a consensus to get rid of this now?
>
> If not, is there any harm in removing the database constraint which is
> attached to this?
>
> We are doing regular data imports from 1.4, and this constraint
> complicates things. I cannot really see where it is used anywhere.
>
> Best regards,
> Jason
>
>
> On Wed, May 2, 2012 at 5:07 PM, Lars Helge Øverland <larshelge@xxxxxxxxx> wrote:
>>
>> Bringing this old thread to life. Seems there is an agreement to remove the
>> alternative name property. First there is no business logic attached to
>> alternative name meaning it can and should be created as an attribute.
>> Second the database internationalization has been fixed and now works well.
>> Third it is making some currently planned changes in the web api harder. So
>> we will remove it.
>>
>> Lars
>>
>>
>> _______________________________________________
>> 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
>>