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's support for direct column name matches is missing in DataClassRowMapper #29187
Comments
@madorb, what databases (and database drivers) did you test this against? In addition, are you using a connection pool, and if so which one(s)? I ask, because I believe the behavior of If you could provide a minimal example application which demonstrates the problem, that would really help us in diagnosing the issue. |
This was SQL server, i haven't touched this project for a while, but if i can find the time i'll try to get a minimal example |
Thanks for the reply, @madorb.
Based on a quick glance at the implementation of the JDBC driver for SQL server, it appears that column name lookups are performed as exact matches and then case-insensitive as a fallback. In light of that, it is a bit unexpected that
That would be great.
As a side note, what exactly do you mean by that? Was there an actual error -- for example, in the form of an Or did the |
If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed. |
Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue. |
This is a follow-on to closed ticket (that I'm unable to reopen) which I believe did not fully address the problem.
After the update the
BeanPropertyRowMapper
's behavior still does not match the documentation fromBeanPropertyRowMapper
which states:The "directly" part of the mapping does not occur. Instead it only attempts to match fully lower-cased values.
Given data class:
and query:
the fields are not mapped.
Mapping happens successfully if either the query is changed to:
OR the data class is changed to:
It seems either the documentation or the behavior of this class should be changed.
The text was updated successfully, but these errors were encountered: