Skip to content
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

GenericCallMetaDataProvider should not treat 'NULLABLE' column as boolean (for compatibility with latest Postgres driver) [SPR-15333] #19896

spring-issuemaster opened this issue Mar 8, 2017 · 0 comments


None yet
2 participants
Copy link

commented Mar 8, 2017

Sean Mills opened SPR-15333 and commented

After upgrading to the latest Postgresql JDBC driver (42.0.0), I ran into a bug while processing call meta data. The meta data ResultSet returns a short type for the 'NULLABLE' column. However, the org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.processProcedureColumns(...) method uses the getBoolean() method. I originally thought this was a problem with the latest Postgresql JDBC driver, but in reviewing the JavaDoc, the getBoolean() method doesn't describe how to handle anything other than NULL, 0, or 1. Since the 'NULLABLE' column can return 2, meaning unknown, the code should change to process the ResultSet with the explicitly defined type.

Affects: 4.3.6

Issue Links:

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

Referenced from: commits cfd9b34, 79ea779

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.