Multiple instances of uniqueness constraints

Submitted by Josef Kaltwasser on Friday, 24 June, 2011 - 13:05
Issue ID
47
Component
Tool
Category
Bug report
Priority
Normal
Assigned
Status
Fixed
Source
Website
Description

The methodology allows for multiple instances of "entry" classes. The tools accepts these multiplte instances and creates an XML element declaration for each of them, as expected. Th eproblem is that the tool includes the same set of unuqueness contraints in all these element declarations. Now these contraints have themselves have to have unque names, but in case of multiple such element declarations, the conatrsaints are also multiplied, using the same names multiply, which is not allowed as far as I know.

Proposal: either create set of contraints only once or give them unque names in all places.

{"changeLogs":[{"date":1528113473958,"assignedOLD":"","assigned":"jaderberg (22)","statusOLD":"- None -","status":"Fixed","priorityOLD":"- None -","priority":"Normal","categoryOLD":"- Select a value -","category":"Bug report","componentOLD":"- Select a value -","component":"Tool"},{"date":1537270146143}]}

Posted by jaderberg on January 18, 2038 Permalink

Solved. All constrains now got a unique name.