SQL 2016 MATCH RECOGNIZE JDBC parameter Marker / Escape Characters
Mark Rotteveel
mark at lawinegevaar.nl
Tue Oct 9 18:23:49 UTC 2018
On 9-10-2018 20:19, Lance Andersen wrote:
> Escape processing cannot be disabled on a PreparedStatement via
> setEscapeProcessing() per the JDBC spec
>
> From the Statement::setEscapeProcesing javadoc
>
> ———————————————
> Note: Since prepared statements have usually been parsed prior to making
> this call, disabling escape processing for |PreparedStatements| objects
> will have no effect.
> —————————————————————
>
> Now that has been a soft assertion but the intent is that it cannot be
> disabled
True, but I was pointing to the fact some drivers provide options to
disable it on a connection level, for example MySQL has
enableEscapeProcessing (default true) and processEscapeCodesForPrepStmts
(default true).
Mark
--
Mark Rotteveel
More information about the jdbc-spec-discuss
mailing list