Conversation
…compatibility option Rejecting nested tuple/array selections in CriteriaBuilder.tuple()/array() drops an OpenJPA extension that applications may rely on. Keep the specification behaviour as default and add the compatibility option AllowNestedCompoundSelection to restore the historic nesting support.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Rejecting nested tuple and array selections is spec-correct, but it dropped an OpenJPA extension that applications may rely on. The rejection is now gated behind the new compatibility option
AllowNestedCompoundSelection, which defaults to the spec behaviour and can be turned on to restore the extension.TestMultiselectcovers both, and the migration guide documents the option.