forked from hibernate/hibernate-orm
-
Notifications
You must be signed in to change notification settings - Fork 0
HHH-19565 #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This file contains hidden or 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
to avoid unnecessary proxy initializan when JPA proxy compliance is enabled
Also fix hsqldb's param rendering
Signed-off-by: Jan Schatteman <[email protected]>
Add @OverRide to includeEntityProperty
because the JDK version is not available in FIPS mode
and eliminate unnecessary use of anon function
…after entity initialization
Add @OverRide to processCollection
- simply delete one which was @Incubating - replace others via deprecation
- getValueConverter() to return JPA AttributeConverter since this is a much less technical interface and is easier for user to implement - had to fix a problem with embeddable discriminators manifesting in JsonHelper and StructHelper and took the opportunity to clean up use of generic types - now probably need efficient impls of isInstance()
change the assertions about how many statements are executed in the cases covered in these tests, the external behavior is portable, which is great. On the other hand, there are also cases where @onDelete(CASCADE) is unportable, and perhaps in those cases we should detect and throw when @onDelete(CASCADE) is used on a platform with no 'on delete cascade' construct (i.e. on Sybase)
previously this was (unnecessarily) disallowed
So that we always set the test release version, in particular.
…r SQM nodes - finally enables efficient caching of criteria query plans - also reconsider how alias generation is done - aliases should only be unique to a given query, NOT globally unique, since that results in interpretation cache misses - ran into and fixed several other problems along the way - note that the previous solution based on translating to HQL was not working at all, partly because the translation to HQL is not very correct - but anyway this is more efficient, since hashCodes are in general more flexible from an efficiency perspective - there is still a remaining problem where NavigablePaths elements are assigned globally unique aliases resulting in cache misses
…oblem - just deprecate the method, since HQL doesn't allow anonymous CTEs - perhaps we need to do the same for the withRescursiveXxxxx() methods - I don't really see a better fix, since nested CTEs can be composed before composing them with the outer query (perhaps we could modify the aliases of all CTEs after the whole query is built)
Oracle disapproves of aliases of form "_1"
… and reenable a check
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.