Interesting hint about jOOQ’s behaviour being akin to CURSOR_SHARING=FORCE. The reason for the current default is obvious: jOOQ cannot distinguish between what reads as a constant literal (i.e. a literal embedded in the jOOQ API) and a variable (i.e. something that has been previously assigned to a local variable). While the difference is clear to the reader of Java code, behind the scenes, it’s all the same jOOQ expression tree.

However, I can see how the value in the LIMIT clause could profit from being inlined by default and made a bind parameter only explicitly by using DSL.val() (unlike OFFSET, which should definitely be a bind parameter by default). I’ve added a feature request to add a setting that would inline the LIMIT value by default: https://github.com/jOOQ/jOOQ/issues/7720