Spring JDBC not correctly processing Postgresql ?| and ?& operator#1366
Merged
jhoeller merged 2 commits intospring-projects:masterfrom Mar 27, 2017
arturgspb:master
Merged
Spring JDBC not correctly processing Postgresql ?| and ?& operator#1366jhoeller merged 2 commits intospring-projects:masterfrom arturgspb:master
jhoeller merged 2 commits intospring-projects:masterfrom
arturgspb:master
Conversation
|
@arturgspb Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
|
@arturgspb Thank you for signing the Contributor License Agreement! |
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
3 participants
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.
JIRA link https://jira.spring.io/browse/SPR-15382
Postgresql has many functional operators such as ?| and ?& (for example [https://www.postgresql.org/docs/9.5/static/functions-json.html]).
Spring JDBC processing for this case is not correct. When running the following SQL:
... I see exceptions like this:
If I use placeholders I see: