Turns out that this is a problem (or at least, a difference) with the driver. For all versions of Oracle that we have ever supported, the syntax
was correct. It looks like 10g dropped the braces in its native client, but JDBC drivers up to and including 11g release 1 would accept either syntax (ie, both with or without the braces). Now, the latest 11g release 2 JDBC driver requires that the braces be omitted.
We have added a server.properties flag, sql.oracle.encloseEscapeClauseInBraces to control whether the braces are included or not. This will make its way into a nightly build today or tomorrow. In the meantime, you could work around the problem by replacing your JDBC driver with a slightly older one - such as this one
Code:
{ ESCAPE '\' }
We have added a server.properties flag, sql.oracle.encloseEscapeClauseInBraces to control whether the braces are included or not. This will make its way into a nightly build today or tomorrow. In the meantime, you could work around the problem by replacing your JDBC driver with a slightly older one - such as this one
Comment