Ticket #84 (defect)
Opened 7 years ago
Last modified 5 years ago
event's organizer has "unique" constraint
Status: closed (wontfix)
|Reported by:||email@example.com||Assigned to:||douglm|
I'm not entirely sure of the purpose of the "organizer" field on Event, but it doesn't seem appropriate that it is unique. Especially since via the webadmin add event screen, the organizer field is set as null on new events. And then when attempting to add a second event, the unique constraint fails because there would be two events with the same organizer: "null".
Details: MSSQL. The constraint in question is:
UQ__events__70698DE3 nonclustered, unique, unique key located on PRIMARY organizerid
The exception thrown is:
ERROR 2006-06-28 10:49:27,020 org.hibernate.util.JDBCExceptionReporter - Violation of UNIQUE KEY constraint 'UQ__events__70698DE3'. Cannot insert duplicate key in object 'events'. DEBUG 2006-06-28 10:49:27,020 org.bedework.calcore.hibernate.CalintfImpl - handleException called ERROR 2006-06-28 10:49:27,067 org.bedework.calcore.hibernate.CalintfImpl - org.bedework.calcore.hibernate.HibSession@154fed2 org.hibernate.exception.ConstraintViolationException: could not insert: [org.bedework.calfacade.BwEventObj] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:69) ...
06/28/06 11:14:29: Modified by firstname.lastname@example.org
- attachment Event.hbm.xml.organizer-unique.patch added.
01/17/07 22:57:44: Modified by douglm
- milestone set to Bedework 3.3.1.
02/13/07 10:12:36: Modified by douglm
- description changed.
- milestone changed from Bedework 3.3.1 to Bedework 3.3.2.
02/22/07 14:01:29: Modified by douglm
- milestone changed from Bedework 3.3.2 to Bedework 3.3.3.
06/26/07 23:14:38: Modified by douglm
- milestone changed from Bedework 3.3.3 to Bedework 3.5.
01/29/08 09:40:44: Modified by douglm
- milestone changed from Bedework 3.5 to Bedework 4.0.
02/25/08 00:24:50: Modified by douglm
- status changed from new to closed.
- resolution set to wontfix.