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

Unable to bind a null value for UUID column with PostgreSQL [SPR-16669] #21210

Closed
spring-projects-issues opened this issue Mar 29, 2018 · 3 comments
Closed
Assignees
Labels
in: data status: backported type: regression
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Mar 29, 2018

Rémi Aubel opened SPR-16669 and commented

PostgreSQL database defines the type UUID (this type does not exist in java.sql.Types).

I want to use this kind of PreparedStatement:

SELECT ... WHERE :VAL IS NOT NULL AND :VAL = <my_uuid_column>

And I want to bind a null value for VAL.
In this specific case, PostgreSQL JDBC driver requires the data type to be specified. And since the UUID data type does not exist in java.sql.Types, we must specify the type name as well, by calling PreparedStatement.setNull(\_, java.sql.Types.OTHER, "uuid").
With plain old java (Connection and PreparedStatement), this works fine.

Using NamedParameterJdbcTemplate (and providing the "data type" and "data type name" in a MapSqlParameterSource), I'm not able to make it work.
Under the hood, StatementCreatorUtils.setNull(\_, \_, type, typeName) delegates to PreparedStatement.setNull(\_, type) (with no type name) when type is Types.OTHER.

Shouldn't it call PreparedStatement.setNull(_, type, typeName) when typeName is provided (non null) instead?


Affects: 4.3.14, 5.0.4

Issue Links:

  • #13215 Can't insert into nvarchar2 using SimpleJdbcInsert whereas it works with SimpleJdbcTemplate

Referenced from: commits 9a722b4, 5629fa2

Backported to: 4.3.15

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Mar 29, 2018

Juergen Hoeller commented

This seems to be a regression introduced in Spring Framework 4.1 (#13215). I'll revise this for the upcoming 5.0.5 and 4.3.14 releases.

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Mar 29, 2018

Juergen Hoeller commented

I've resolved this through not entering our fallback block in case of Types.OTHER with a non-null typeName, going to the usual PreparedStatement.setNull variant with a type name again.

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Mar 30, 2018

Rémi Aubel commented

Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data status: backported type: regression
Projects
None yet
Development

No branches or pull requests

2 participants