Fix parsing entity names in JPQL query with package names that contain reserved words #3457
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
…n reserved words.
… reserved exp keyword.
christophstrobl
force-pushed
the
issue/3451
branch
from
963e79d to
126b31d
Compare
…n reserved words.
|
Not sure if this PR handles the reserved words anywhere in the query, but I found that the table alias couldn't be the reserved word either. |
It isn't intended but permits reserved words as per JPA spec, identifiers are:
Isn't the purpose of reserved words that you cannot use these in arbitrary places? |
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.
Resolves: #3451