From e9027c990682a470ab89ecb83cfc5ce3dc51bc74 Mon Sep 17 00:00:00 2001
From: Javier Moran Rua <jmoran@igalia.com>
Date: Thu, 15 Oct 2009 22:51:32 +0200
Subject: [PATCH] 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.
---
 .../navalplanner/business/calendars/entities/Calendars.hbm.xml  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/navalplanner-business/src/main/resources/org/navalplanner/business/calendars/entities/Calendars.hbm.xml b/navalplanner-business/src/main/resources/org/navalplanner/business/calendars/entities/Calendars.hbm.xml
index 13162c42a..e2a35f912 100644
--- a/navalplanner-business/src/main/resources/org/navalplanner/business/calendars/entities/Calendars.hbm.xml
+++ b/navalplanner-business/src/main/resources/org/navalplanner/business/calendars/entities/Calendars.hbm.xml
@@ -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" />