Hello, You're right, nice catch. The Javadoc is incorrect, and has been so for a while. I have created an issue for this: https://github.com/jOOQ/jOOQ/issues/4563
Also, jOOQ doesn't behave exactly as one might expect when looking at things from a JavaBeans perspective. If both a setter AND a field match a given column, they will both be set individually, regardless of their visibility. I hope this helps, Lukas 2015-09-15 13:33 GMT+02:00 jdoe <[email protected]>: > Hello! > > I've discovered that when my DB field has name *some_name* than my setter > *setSomeName(...)* will be invoked for mapping, but when I give my > selected field the *someName* alias than the respective bean property > will be set without touching the mentioned setter even if its backed field > has private access modifier. But javadocs for DefaultRecordMapper states > that only public fields will be respected: > > > - Public non-final instance member field MY_field > - Public non-final instance member field myField > > What do I miss? > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
