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

Spring JDBC not correctly processing Postgresql ?-contained operator [SPR-13582] #18159

Closed
spring-issuemaster opened this Issue Oct 16, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

spring-issuemaster commented Oct 16, 2015

Artur Geraschenko opened SPR-13582 and commented

Postgresql has many functional operators such as ? (for example JSONB operators).

Spring JDBC processing for this case is not correct. When running the following SQL:

SELECT '["1","2","3"]'::jsonb ? '4'

... I see exceptions like this:

class org.springframework.dao.InvalidDataAccessApiUsageException
SQL [SELECT '["1","2","3"]'::jsonb ? '4']: given 1 parameters but expected 0

In pgjdbc this bug was fixed in 2014 (pgjdbc/pgjdbc#227).


Affects: 4.2.2

Reference URL: #892

Issue Links:

  • #21054 Spring JDBC not correctly processing Postgresql ? operator
  • #19945 Spring JDBC not correctly processing Postgresql ?| and ?& operator

Referenced from: commits 11d1f05

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

spring-issuemaster commented Oct 17, 2015

Artur Geraschenko commented

I fix it #892

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

spring-issuemaster commented Oct 18, 2015

Artur Geraschenko commented

Juergen, hello! I really want to get this fix in the near release, whether it is possible to speed up the adoption of the revisions?

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

spring-issuemaster commented Oct 26, 2015

Juergen Hoeller commented

Rolling this into 4.2.3 now, to appear in the 4.2.3.BUILD-SNAPSHOT...

Juergen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment