I think I would just remove this test case, as the other tests you will
be adding definitely will test the new ability and behavior of creating
unique constraints on a nullable field. I would not hold up a checkin
based on this.
Anurag shekhar wrote:
After enabling unique constraint on nullable fields db2
compatibility tests are failing because they expect failure while
creating unique constraint over null able fields.
For now I have modified the out file (Attached separately in DERBY-3330,
db2Compatibility.diff )
Is it right thing to do ? or Shall I modify the test itself to stop
testing unique constraint
over null able fields ?
thanks
anurag
