-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Overloaded postgres routine missing schema qualification on parameter cast in 3.9.0 #5798
Comments
Thank you very much for reporting. I wonder why the second (outer) cast is added, the first one (inner) ought to be sufficient |
Agreed. The workaround I've used is to rename the second function. Without the overloading the generated sql is fine. Haven't captured the good sql, however. |
With jOOQ 3.18, I cannot reproduce this anymore. The logged SQL is:
I remember having fixed related issues recently. It's also integration tested now. |
If a postgres function is overloaded with a schema specific parameter type in one signature, the generated invocation sql is missing a schema qualifier. E.g. given:
Invoking the second signature generates something along the lines:
select "function" from "foo"."function"("arg1" := cast($1::"fb"."bartype" as bartype)
But the type named in the cast needs to be qualified relative to schema foo.
Worked ok in 3.8.6.
The text was updated successfully, but these errors were encountered: