Support converting underscores column name to camel case property name for projecting native query #3472
Conversation
spring-projects-issues
added
the
status: waiting-for-triage
| @@ -378,6 +403,14 @@ public boolean containsKey(Object key) { | |||
| tuple.get((String) key); | |||
| return true; | |||
| } catch (IllegalArgumentException e) { | |||
| if (nativeQuery) { | |||
| try { | |||
| tuple.get(JdbcUtils.convertPropertyNameToUnderscoreName((String) key)); | |||
There was a problem hiding this comment.
Instead of customizing the Map, it would make sense to have a custom Tuple wrapper that handles the conversion.
Consider a tuple that would contain first_name and firstName elements. It is impossible to tell in which order these should appear in a map nor which value to return in a Set<Map.Entry>.
Attempting snake-case to camel-case conversion on value absence makes sense, for the rest we should keep the functionality as-is.
The Tuple wrapper would delegate all enumerative calls to the Tuple delegate while get(…) calls are augmented for property name conversion.
There was a problem hiding this comment.
Good point, updated now, please review again.
…e for projecting native query > By default, Spring Boot configures the physical naming strategy with CamelCaseToUnderscoresNamingStrategy. Then we should convert underscores back to camel case. Fix spring-projectsGH-3462
mp911de
added
type: enhancement
|
Thank you for your contribution. That's merged and polished now. |
Then we should convert underscores back to camel case.
Fix GH-3462