Iron fails with multiple Unique Constraints

[sdaclin]

Reproduction Steps
Using an object definition with 2 @unique constraints (like SourcePO.class on uniqueName and secret fields)
Create a 1st entry (uniqueName = name1, secret = secret1)
Create a 2nd entry with a violation (uniqueName = name2, secret = secret1 or uniqueName = name1, secret = secret2)) -> should raise an expected error
Create a 3rd entry without violation (uniqueName = name2, secret = secret2)

Actual result
The 3rd entry creation is failing because of a supposed Unique Constraint Violation

Expected result
The 3rd entry is correctly stored

[sdaclin]

Fixed