mention constraints which Hibernate doesn't actually create due to bug
This commit is contained in:
parent
faa8e2bb9b
commit
02b551464d
|
@ -927,7 +927,7 @@ Collection<Book> books;
|
|||
[NOTE]
|
||||
.`Set`, `List`, or `Collection`?
|
||||
====
|
||||
A one to many association mapped to a foreign key can never contain duplicate elements, so `Set` seems like the most semantically correct Java collection type to use here, and so that's the conventional practice in the Hibernate community.
|
||||
A one-to-many association mapped to a foreign key can never contain duplicate elements, so `Set` seems like the most semantically correct Java collection type to use here, and so that's the conventional practice in the Hibernate community.
|
||||
|
||||
The catch associated with using a set is that we must carefully ensure that `Book` has a high-quality implementation of <<equals-and-hash>>.
|
||||
Now, that's not necessarily a bad thing, since a quality `equals()` is independently useful.
|
||||
|
|
|
@ -264,6 +264,8 @@ class Book {
|
|||
}
|
||||
----
|
||||
|
||||
Here, there should be a `UNIQUE` constraint on one of the columns of the association table.
|
||||
|
||||
[source,java]
|
||||
----
|
||||
@Entity
|
||||
|
@ -276,6 +278,8 @@ class Author {
|
|||
}
|
||||
----
|
||||
|
||||
Here, there should be a `UNIQUE` constraint on _both_ columns of the association table.
|
||||
|
||||
.`@JoinTable` annotation members
|
||||
[cols=",8"]
|
||||
|===
|
||||
|
|
Loading…
Reference in New Issue