@UniqueConstraint

[Tomek Brzeczyszczykiewicz]

Hi,

having in the code:

@Table(name="contact", uniqueConstraints = @UniqueConstraint(columnNames = {"code","customer_code"}))

and later in the class:

@Column(name="code", nullable=false, length=20, unique=false)
@NotNull
private String code;

Can any one explain why in postgres it's generating two constraints:
- contact_code_key UNIQUE (code, customer_code),
- contact_code_key1 UNIQUE (code)

should it be just first one? or I'm missing something here?

Thanks for any help
Tomek

[Mark Spritzler]

"Tomek ABCDF"

Please click on the My Profile link above and change your display name to meet the JavaRanch Naming Policy of using your real first and real last names.

Thank you for your understanding.

Mark

[Mark Spritzler]

That is interesting consider that you specifically said that one field itself is not unique.

So, we can gather that the first constraint is in regards to the class level annotation.

The second one should just have that it cannot be null and nothing about it being unique. What happens when you remove the unique=false part?

Mark

[Tomek Brzeczyszczykiewicz]

Thanks for your replay.

I found is the problem.

in Order entity I have:

public Order {
...
 
@ManyToOne(fetch=FetchType.LAZY)
@JoinColumn(name="contact_code", referencedColumnName="code", nullable=false)
private Contact contact;
 
...
}

so it assumes that the column must be unique, and I understand why, but is there anyway to get around this?

Thank you,
Tomek