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

BeanPropertyRowMapper should default primitive property when receiving null value from result [SPR-5588] #10259

Closed
spring-projects-issues opened this issue Mar 20, 2009 · 0 comments
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Greg Nieman opened SPR-5588 and commented

Submitted on behalf of support client:

BeanPropertyRowMapper should gracefully handle null return values for primitive types. Currently it will attempt to set the null value into the target bean, treating the primitive property the same way it would an Object property. In such cases, a pre-established default value would allow the retrieval to proceed. Currently the SQL for retrievals where this may occur require modification to add NVL() for all numeric fields that have the potential to be null.


Affects: 3.0 M2

Referenced from: commits 360434d, 93c56f1

@spring-projects-issues spring-projects-issues added in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0 M3 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

1 participant