abstractdatabaseoperationevent #2
Closed
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
This reverts commit cd1755f.
also remove unnecessary use of reflection for creation of the CDI BeanContainer
…ions via PersistenceContext Hibernate Reactive needs a reactive version of the PersistenceContext to load non-lazy collections. But, now that `SatefulPersistenceContext` is package-private, Hibernate Reactive cannot extend the class anymore. These change make it possible to access the internal snapshots, so that the reactive implementation can implement the interface and doesn't need to extends `SatefulPersistenceContext`.
…ceptionConversionDelegate#convert returns null
…rnate.atlassian.net/browse/HHH-18933 - showing the issue has been resolved
…/2024/07/12/embeddable-inheritance/ - showing the issue has been resolved
…llocate extra space
for discriminator column(s) when input parameter is null and
number of discriminator columns greater than zero
The problem was that you had a different SQL query depending on the order the fetch and join operations were created when defining a criteria query. For example: ``` // Example 1: Root<Book> from = criteriaQuery.from( Book.class ); Fetch<Object, Object> fetch = from.fetch( "authors" ); Join<Object, Object> join = from.join( "authors" ); ``` it was different than ``` // Example 2: Root<Book> from = criteriaQuery.from( Book.class ); Join<Object, Object> join = from.join( "authors" ); Fetch<Object, Object> fetch = from.fetch( "authors" ); ``` In the first example, `fetch` and `join` were exactly the same object, causing issues if the association `authors` appeared in the `where` clause. For example: ``` criteriaQuery.where( cb.equal( join.get( "id" ), 2L ) ); ``` Note that now we always rung an extra join even when not necessary. But this is consistent with what happen with HQL, and we can figure out how to add this improvement in a different issue.
This reverts commit d9289c1.
Re-work test added by hibernate@3292a83
While collecting they are inserted in proper order, but TreeMap will
not preserver ordering, but sort them alphabetically by names.
To keep values order LinkedHashMap should be used instead of TreeMap.
note that this feature was most likely introduced in HHH-10431 by accident!
…e format HHH-19237 - Expand graph language to optionally specify entity HHH-19217 - Expose GraphParser#parse on SessionFactory
* HHH-19140 Add test case * HHH-19140 Fix for issue
1. delete unused class SaveOrUpdateEvent 2. introduce AbstractPostDatabaseOperationEvent for consistency 3. DirtyCheckEvent should no longer extend FlushEvent
because the Pre and Post versions were isomorphic
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.
[Please describe here what your change is about]
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.