-
Notifications
You must be signed in to change notification settings - Fork 8
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
CAST types passed as strings #4
Comments
I'm having a déjà vu. I can feel with you :-) |
As my grandmother used to say, 9 times out of 10, you should just use JOOQ and be done with it. On the 10th time you might think about porting it to another platform, but you then you still use JOOQ. |
What a wise grandmother! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, to cast a field to a given type, you need to supply the string representation of the underlying SQL type. This is neither type safe nor portable. We should introduce a strongly typed representation that can be adjusted for target dialects.
The text was updated successfully, but these errors were encountered: