[CONJ-1028] Connector implicitly switching noBackslashEscapes flag from false to true in protocol Created: 2022-11-24 Updated: 2023-11-06 |
|
| Status: | Needs Feedback |
| Project: | MariaDB Connector/J |
| Component/s: | None |
| Affects Version/s: | 2.7.6, 3.1.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Cloud Ops | Assignee: | Diego Dupin |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When connector runs a prepared statement which contains backslash in where clause parameter. e.g.
It works fine for sometime till noBackslashEscapes flag is false in connector protocol. But then noBackslashEscapes flag implicitly changed to true and connector stopped escaping backslash character in query. When query is executed on server it takes the backslash character as escape character and doesn't return the expected result. Note: The NO_BACKSLASH_ESCAPES mode is disabled on MariaDB server. |
| Comments |
| Comment by Diego Dupin [ 2022-12-23 ] |
|
I don't understand why NO_BACKSLASH_ESCAPES would be set to true unexpectedly, connector use server flag to set/change value. |
| Comment by Cloud Ops [ 2023-01-16 ] |
|
Hi Diego, |