dhis2-devs team mailing list archive

[Knut Staring <knutst@xxxxxxxxx>]

2009/11/15 Lars Helge Øverland <larshelge@xxxxxxxxx>

I disagree. The systems depends in some places on short-names actually
> being short, eg. like in report tables where the output will become
> cumbersome with long names.


They may become cumbersome - but the application will not fail.

So your proposal is to keep the length but remove the uniqueness?


> Whether it is clever to have such a
> constraint is another discussion, but we cannot have dissimilarities
> between the API and the database constraints.
>

Perhaps not, but what I propose is to limit to 230 characters also in the
API, but have an administrative setting which further restricts any new
names and edits in the GUI. Still, you have a point that if people set this
restriction to something shorter than the longest name in the database, they
should perhaps be given some assistance in dealing with the long names (if
the choose to), such as an alphabetical list of just these names with edit
links.

>
> ** Changed in: dhis2
>    Milestone: 2.0.3 => None


When I look at this bug in LP,it seems to still have Milestone 2.0.3  -
strange.

Knut


> --
>
> Orgunit shortname field should be as long as name field in db
> https://bugs.launchpad.net/bugs/483096
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in DHIS 2 - District Health Information Software: New
>
> Bug description:
> Having the shortname field in the database limited to only 25 characters
> makes it hard to import facilities (especially in combination with the other
> constraints of NOT NULL and UNIQUE (the latter should be removed, see
> https://bugs.launchpad.net/dhis2/+bug/370791).
>
> If we do want to limit the lengths of shortnames users can enter, this
> should be an administrative setting.
>



-- 
Cheers,
Knut Staring



-- 
Cheers,
Knut Staring