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
DefaultRecordUnmapper cannot unmap a POJO into its corresponding UDTRecord #6917
Comments
Thank you very much for your report. Would you mind posting the stack trace as well here, for completeness' sake? |
gladly:
|
Thanks again for your nice minimal test case. I can reproduce the issue and the stack trace. Will now look into this. |
This doesn't seem strictly dependent on using DAOs. It simply doesn't work with any way the |
Indeed, recursive unmapping is simply not supported at this moment. Will look more into this next week. |
The relevant integration test is no longer failing due to a recent fix. There had been a few |
It looks like the test should have passed a while ago already, but because the integration tests didn't turn on generating I'm closing this issue as fixed |
I tried again with the MCVE, the issue still persists:
Perhaps the integration test was testing something else |
I see now. The improvements that fixed the problem here were:
Both were implemented in jOOQ 3.15.0. Closing this as a duplicate of the above two. |
Expected behavior and actual behavior:
Expected: generated POJOs for Postgres custom types should be usable in generated DAOs
Actual: org.jooq.impl.DAOImpl.insert throws a MappingException
Steps to reproduce the problem:
I've created a small maven project to demonstrate, see the attached zip file
jooqmve-master.zip, or clone
https://github.com/nsn/jooqmve
Versions:
The text was updated successfully, but these errors were encountered: