Uniqueness check for translations

Registered by Lars Helge Øverland on 2010-04-13

Currently there is no check for uniqueness when adding translations for properties which are unique in the "main" tables. Eg you can't add two DataElements with the same name but its possible to add two translations of the DataElement names that are equal. There should be a way of defining which properties are unique on the I18nObject, and there should be a uniqueness validation check when adding translations for those properties.

Blueprint information

Status:
Complete
Approver:
Lars Helge Øverland
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Hieu Duy Dang
Definition:
New
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 2.0.5
Started by
Hieu Duy Dang on 2010-04-28
Completed by
Lars Helge Øverland on 2010-07-25

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.