You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our parser supports parsing JDBC escape syntax by default, which is a reasonable default for usage as a JDBC proxy (the ParsingConnection), but it might be undesired in other situations, e.g. when working with the ParserCLI from non-Java environments.
jOOQ 3.20 now supports the PostgreSQL ? operator that maps to jsonb_exists:
As such, we'll parse both ? and ?? as valid operators when working with the JDBC escape syntax. ? is supported in static statements, and ?? only in prepared statements.
Other JDBC escape syntax will also be affected. The default flag value is true for backwards compatibility reasons.
The text was updated successfully, but these errors were encountered:
Our parser supports parsing JDBC escape syntax by default, which is a reasonable default for usage as a JDBC proxy (the
ParsingConnection
), but it might be undesired in other situations, e.g. when working with theParserCLI
from non-Java environments.jOOQ 3.20 now supports the PostgreSQL
?
operator that maps tojsonb_exists
:Within JDBC, that operator has to be escaped as
??
, see:As such, we'll parse both
?
and??
as valid operators when working with the JDBC escape syntax.?
is supported in static statements, and??
only in prepared statements.Other JDBC escape syntax will also be affected. The default flag value is
true
for backwards compatibility reasons.The text was updated successfully, but these errors were encountered: