dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

Hi Aravind,

good point. There is actually a Hibernate-managed uniqueness constraint
covering both datasetid + name, and hence there should not be a uniqueness
constraint on name only. I have removed it in trunk and 2.15 now.

Does this imply that you do not need attributes for sections?

regards,

Lars



On Mon, May 5, 2014 at 12:38 PM, Aravind Muralikrishnan <
aravindm@xxxxxxxxxxxxxxxx> wrote:

> Hello all,
>
> We are customising DHIS2 for MSF, and we have a scenario in which we have
> 2 different data sets having a data set section each, with the same name.
>
> Ex:
> * Consultation (Data set section) under OPD-General (Dataset)
> * Consultation (Data set section) under OPD-Chronic (Dataset)
>
> We saw that we have a unique constraint on the data set section name.
>
> Also when we tried to work around this by trying to add an attribute to
> dataset section, called "display name", we found out that, we cannot add
> attributes to dataset section.
>
> Is there another way to model this?
> Also it would be helpful for us to understand the rationale behind the
> unique constraint on data set section name, and attributes for data set
> section.
>
> Thanks,
> Aravind
>
> _______________________________________________
> 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
>
>