Grails

Compound "unique" constraints incorrectly pass validation if one of the fields is null

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 1.2-M2
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Testcase included:
    yes

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Graeme Rocher added a comment -

There is no scope / time to resolve these remaining lower priority issues for 1.2 so moving to 1.3

for 1.2 final only issues considered blocking will now be fixed

Show
Graeme Rocher added a comment - There is no scope / time to resolve these remaining lower priority issues for 1.2 so moving to 1.3 for 1.2 final only issues considered blocking will now be fixed
Hide
Permalink
Benjamin R. Doerr added a comment - - edited

Unit tests at least still show that this is an issue in 1.3.7. Could this be scoped for 2.0?

Show
Benjamin R. Doerr added a comment - - edited Unit tests at least still show that this is an issue in 1.3.7. Could this be scoped for 2.0?
Hide
Permalink
James Kleeh added a comment -

I was still having this issue very recently and it was a pain to work around. Any chance this can get fixed?

Show
James Kleeh added a comment - I was still having this issue very recently and it was a pain to work around. Any chance this can get fixed?
Hide
Permalink
allnightlong added a comment -

+1 for fix this bug (although it seems more like hibernate issue)

Show
allnightlong added a comment - +1 for fix this bug (although it seems more like hibernate issue)

People

  • Assignee:
    Unassigned
    Reporter:
    Marc Palmer
Vote (15)
Watch (12)

Dates

  • Created:
    Updated:
    Last Reviewed: