-
-
Notifications
You must be signed in to change notification settings - Fork 336
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
@ColumnName just working on val, not var properties intentional? #1207
Comments
Just to be clear, we're talking about the Kotlin mapper, correct? |
Yes, all Kotlin including the mapping. The example being a
The column name in the (PostgreSQL 9.6) database is
..except turning the var into a val. The odd thing is that a separate test setup within the same project has this working with either val or var:
If this is not supposed to happen, can it have to do with the BigDecimal type? |
IGNORE THIS COMMENT, IT'S OBSOLETE, SEE @Nunobpinto'S COMMENT BELOW. Notice the test I set up within the same project as above.
This works fine:
Versions:
|
I have the exact same problem. Regarding why there's no error when you try to map this class:
That's because the property |
I fixed most of my cases by registering my row mappers with However this is only when I am creating queries within code and not in a Dao interface, I've had weird results when using Dao's. |
@ivanfeli so could you provide a code sample where jdbi fails or is there no more issue? |
I've tried this in local testing and have yet to find a failing case. @jmbremer Could you provide a standalone example that demonstrates the problem? |
I can't reproduce the error reported and #1506 adds test validating those findings. Please feel free to open a new issue if this is still a problem--preferably with a test case that we can use to reproduce it. |
As the title says: Am I missing something in finding @ColumnName to work fine on val properties (within a data class in this case), but being completely ignored when switching the same property over to var? What's the hint in the documentation that I am noobishly missing? Thank you!
The text was updated successfully, but these errors were encountered: