Message Title

Ted Bergeron commented on an issue

7 years since opening, very detailed explanations in the comments, a limitation that still exists today, then just closed without much explanation. Is there a way now to better handle the items discussed in October, 2006? Is there something in the design philosophy that this goes against?

Add Comment

Hibernate ORM /

HHH-4360

The current way to define a composite unique constraint is limiting.

@Table(name="tbl_sky",
uniqueConstraints = {@UniqueConstraint(columnNames={"month", "day"})}
)

Suppose I have an abstract base class called A that gives me Id and Name, subclassed by abstract class B that gives me Customer. Then I have many concrete classes that subclass B. For a...

This message was sent by Atlassian JIRA