HHH-12687 : Update migration guide
This commit is contained in:
parent
8fff54d6ee
commit
02ff1484be
|
@ -102,6 +102,26 @@ The main gist is that EnhancementTask was fixed (through a contribution) to actu
|
|||
change.
|
||||
|
||||
|
||||
=== Many-to-one association in embeddable collection elements and composite IDs
|
||||
|
||||
A bug introduced in 4.3 caused many-to-one associations in embeddable collection elements and
|
||||
composite IDs to be eagerly fetched, even when explicitly mapped as lazy.
|
||||
|
||||
This bug does not affect many-to-one associations that are not in a composite ID or embeddable
|
||||
collection element.
|
||||
|
||||
In 5.3.2, this bug was fixed. As a result, such associations will be fetched as specified
|
||||
by their mappings.
|
||||
|
||||
Many-to-one associations mapped by using native HBM xml are lazy by default. In order to keep
|
||||
the associations eager in 5.3.2 and later, mappings will need to explicitly specify that
|
||||
they are non-lazy.
|
||||
|
||||
When mapped with annotations, many-to-one associations use `FetchType.EAGER` by default.
|
||||
Starting in 5.3.2, if an association is mapped with `FetchType.LAZY`, the assocation will
|
||||
be lazily fetched, as expected.
|
||||
|
||||
See details on the https://hibernate.atlassian.net/browse/HHH-12687[HHH-12687] Jira issue.
|
||||
|
||||
=== 5.3 -> 6.0 compatibility changes
|
||||
|
||||
|
|
Loading…
Reference in New Issue