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.

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

Support JSR 310 types as <name/> in <forcedType/> data type rewriting feature #8493

Closed
lukaseder opened this issue Apr 5, 2019 · 1 comment

Comments

@lukaseder
Copy link
Member

This currently doesn't work:

<forcedType>
    <name>LOCALDATETIME</name>
    <types>DATE.*</types>
</forcedType>

This does:

<forcedType>
    <name>TIMESTAMP</name>
    <types>DATE.*</types>
</forcedType>

The manual's section about data type rewriting indicates that any SQLDataType literal can be used as <name/>:
https://www.jooq.org/doc/latest/manual/code-generation/data-type-rewrites

This should include synthetic data types.


See also:
https://stackoverflow.com/q/55510060/521799

@lukaseder lukaseder added this to the Version 3.12.0 milestone Apr 5, 2019
lukaseder added a commit that referenced this issue Apr 9, 2019
…ewriting feature

Some SQLDataTypes are "synthetic" aliases of other types, and as such could not yet be used as forcedType names because they were not recognised, despite what the manual says.
@lukaseder
Copy link
Member Author

lukaseder commented Apr 9, 2019

Implemented in jOOQ 3.12. Backport scheduled for 3.11.12 (#8501)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant