ItEr30S17ValidacionEProbasFuncionais: Partial fix of bug #48
Remove unique name constraint in BaseCalendar. This is necessary in order that two resource can have his calendar with the same name as another calendar of other resource. The unique name restriction must be only checked among the BaseCalendar which are not ResourceCalendars.
This commit is contained in:
parent
7496470d80
commit
e9027c9906
1 changed files with 1 additions and 1 deletions
|
|
@ -12,7 +12,7 @@
|
|||
</id>
|
||||
<version name="version" access="property" type="long" />
|
||||
|
||||
<property name="name" access="field" unique="true" />
|
||||
<property name="name" access="field"/>
|
||||
|
||||
<set name="exceptions" access="field" cascade="all-delete-orphan">
|
||||
<key column="BASE_CALENDAR_ID" />
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue