[HHH-18993] modify the user guide in documentation. #9521
+3
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[Please describe here what your change is about]
Regarding the outdated API references, I made the following changes in three adoc files:
Before: The default is to use a batch sizing strategy defined by the Dialect.getDefaultBatchLoadSizingStrategy() method.
After: The default is to use a batch sizing strategy defined by the configuration settings in Hibernate.
Before: As a hopefully temporary legacy hold-over, it is currently required that all lazy singular associations (many-to-one and one-to-one) also include @LazyToOne(LazyToOneOption.NO_PROXY).
After: For existing codebases, it is recommended to remove usages of @LazyToOne, such as
@LazyToOne(LazyToOneOption.NO_PROXY)
, and instead rely on default lazy loading behavior or explicitly configure fetch strategies using @OnetoOne or @manytoone annotations with fetch = FetchType.LAZY where necessary, such as@OneToOne(fetch = FetchType.LAZY)
.Before: If the version number is generated by the database, such as a trigger, use the annotation @org.hibernate.annotations.Generated(GenerationTime.ALWAYS) on the version attribute.
After: If the version number is generated by the database, such as a trigger, implement a custom generator by extending the OnExecutionGenerator interface, and apply it to the version attribute using a custom annotation. Refer to the Hibernate documentation for the latest guidelines on handling database-managed attributes.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.
https://hibernate.atlassian.net/browse/HHH-18993