SQLServer and Bedework
Dave Brondsema at Cornerstone added some related tickets.
Much of the work doen fro Oracle might help here. At the moment there is at least one outstanding problem related to unique constraints.
Standard sql specifies that two nulls are always not equal. This allows a unique constraint to be placed on a column which contains mnay nulls and this is the hibernate suggested approach to specify a one-to-one relationship as in, for example, the event organizer.
However, SQLServer does not follow this standard and the unique constraint causes an exception.
We need to investigate a work-round. SImply removing the constraint may be enough, though it does help to catch bugs. In general we should be checking for uniqueness before adding entries as this provides better error reporting.
In addition, for the organizer, the actual data values m e identical. What is unique is the id.