Rebase to tag 5.6 #2
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tIdentifierGenerator getters
…rtGeneratedIdentifierDelegate
…InsertionCapableIdentifierGenerator
…ositeNestedGeneratedValueGenerator.GenerationPlan
…n is thrown by Batch#addToBatch Such an exception can be thrown if an expectation (org.hibernate.jdbc.Expectation) is not met, for example if an update statement for a given entity affects 0 rows (e.g. because of a concurrent update).
…JDBC batch fails Not strictly necessary, but it's related to these changes and I think it's a good idea.
…when de-referenced in HQL/Criteria - `@NotFound` no longer exports a physical foreign-key
…when de-referenced in HQL/Criteria - `@NotFound` no longer exports a physical foreign-key - tests showing bugs and inconsistencies wrt `@NotFound` handling
…when de-referenced in HQL/Criteria - `@NotFound` no longer exports a physical foreign-key - tests showing bugs and inconsistencies wrt `@NotFound` handling - added `FetchNotFoundException` - force association to EAGER
…when de-referenced in HQL/Criteria - `@NotFound` no longer exports a physical foreign-key - tests showing bugs and inconsistencies wrt `@NotFound` handling - added `FetchNotFoundException` - force association to EAGER
…en de-referenced in HQL/Criteria
…when de-referenced in HQL/Criteria
- `@NotFound` no longer exports a physical foreign-key
- tests showing bugs and inconsistencies wrt `@NotFound` handling
- added `FetchNotFoundException`
- consider a to-one nullable if either:
- explicitly marked nullable
- `@NotFound` is specified, whether IGNORE or EXCEPTION
- force association to EAGER
…TDs in LocalXmlResourceResolver
…when de-referenced in HQL/Criteria - code clean-up
…this issue Signed-off-by: Jan Schatteman <[email protected]>
…etrieved from ServiceRegistry
…SQLQuery visible in Eclipse Explicitly add the JavaDoc to Session.java to provide users the @deprecated JavaDoc hint on how to resolve the deprecation warnings. Without this patch, e.g., in Eclipse, there are no warning generated when the method createSQLQuery is used which makes upgrading to 6.x harder. Signed-off-by: Sven Strickroth <[email protected]>
…tter test reports
…enhancement enabled
…enhancement enabled
…cement enabled results in unnecessary SQL Update in some (many) cases
Signed-off-by: Jan Schatteman <[email protected]>
…dropping catalogs/schemas
…n defined in mappersuperclass with generics
…at use the https scheme
Older versions cannot correctly resolve dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bringing latest changes from original repo on branch 5.6.