2016-06-05 21:10 GMT+03:00 Andrey Antukh <[email protected]>: > Hi Lukas, > > I understand, but I have a question regarding that issues: > > I understand that inference of a type at rumtime can be a problem but null > is almost in all cases is null (I mean no casting is necessary). Maybe a > partial fix to that have a special case for null in jOOQ, and forward it to > the database as null without any special casting. Maybe I'm missing > something of jOOQ internals about this... >
Not every database will agree with this :) and unfortunately, changing these things inside of jOOQ might yield difficult to foresee regressions, so I'm not removing the cast lightly, even if I can see that it is clearly wrong in your case. There's a pending feature request to let users turn off all of these bind variable casts at their own risk, but it has not been implemented yet: https://github.com/jOOQ/jOOQ/issues/1735 I have registered an issue for this. I'm afraid I cannot give you any further feedback on how to work around this right now, I'll have to investigate more deeply first: https://github.com/jOOQ/jOOQ/issues/5345 > Also it seems that this issue appears on the last major release of jOOQ, I > have't observed that in previous releases (maybe I'm wrong, because I'm not > extensive user of the DSL, personally I use jOOQ just for execute plain > sql). > That could be. In PostgreSQL, casts are necessary: - For some specific data types - For function calls (to disambiguate overloads) -- 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.
