Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Escaping can be a real source of slowdown for very large query.
JDBC permit a solution with statement.setEscapeProcessing, to indicate to avoid escaping (to be called prior to execution).
This task is to implement this method.
example of use :
try (Statement stmt = connection.createStatement()) { |
statement.setEscapeProcessing(false); |
statement.execute(myVeryLargeQuery);
|
}
|
Attachments
Issue Links
- relates to
-
CONJ-785 jdbc insert query throws SQLSyntaxErrorException (unknown escape sequence) with 2.6.0 j-connector
-
- Closed
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description | Implements [statement.setEscapeProcessing|https://docs.oracle.com/en/java/javase/11/docs/api/java.sql/java/sql/Statement.html#setEscapeProcessing(boolean)], so in order to avoid escaping, statement.setEscapeProcessing(false) might be called. |
Escaping can be a real source of slowdown for very large query.
JDBC permit a solution with [statement.setEscapeProcessing|https://docs.oracle.com/en/java/javase/11/docs/api/java.sql/java/sql/Statement.html#setEscapeProcessing(boolean)], to indicate to avoid escaping (to be called prior to execution). This task is to implement this method. example of use : {code:java} try (Statement stmt = connection.createStatement()) { statement.setEscapeProcessing(false); statement.execute(myVeryLargeQuery); } {code} |
| issue.field.resolutiondate | 2020-06-22 15:03:54.0 | 2020-06-22 15:03:54.393 |
| Component/s | JDBC compatibility [ 15304 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 110326 ] | MariaDB v4 [ 128421 ] |