GRAILS-5101: Compound "unique" constraints incorrectly pass validation if one of the fields is null

[graemerocher]

Original Reporter: wangjammer5
Environment: Not Specified
Version: 1.2-M2
Migrated From: http://jira.grails.org/browse/GRAILS-5101

[graemerocher]

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

[graemerocher]

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

[graemerocher]

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

[graemerocher]

cake said:
Still an issue in Grails 2.2.3

[droggo]

This is probably not a bug. It depends on database engine how unique index with null value works. For example for mysql unique will never fail if any of the values is null

[apremkumar]

I am facing this as well. I'm using postgresql 9.5, grails 3.3.0, gorm 6.1.6.