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.

Sign up for GitHub

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

Jump to bottom

Let BeanPropertyRowMapper subclasses customize mapped names #32199

Closed
jhoeller opened this issue Feb 5, 2024 · 0 comments
Closed

Let BeanPropertyRowMapper subclasses customize mapped names #32199

jhoeller opened this issue Feb 5, 2024 · 0 comments
Assignees
@jhoeller
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement
Milestone
6.1.4

Comments

@jhoeller
Copy link
Contributor

jhoeller commented Feb 5, 2024 •
edited by sbrannen

BeanPropertyRowMapper traditionally maps lower-case and underscore-based names for each discovered property.

While it allows for customizing those specific names, it does not allow for totally custom mapped names, e.g. derived from a custom annotation.

See the use case described in the tests for #30180.
@jhoeller jhoeller added in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement labels Feb 5, 2024
@jhoeller jhoeller added this to the 6.1.4 milestone Feb 5, 2024
@jhoeller jhoeller self-assigned this Feb 5, 2024
@jhoeller jhoeller mentioned this issue Feb 5, 2024
Closed
jhoeller added a commit that referenced this issue Feb 6, 2024
@jhoeller
Rely on HashSet for uniqueness of mapped names
341ac76 
See gh-32199
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jhoeller jhoeller

Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement
Projects
None yet
Milestone
6.1.4
Development

No branches or pull requests
1 participant
@jhoeller