MySQL Bugs: #7374: Future compatibility with NO_BACKSLASH

Bug #7374	Future compatibility with NO_BACKSLASH_ESCAPE server option
Submitted:	17 Dec 2004 2:52	Modified:	25 Jun 2013 21:34
Reporter:	Ken Johanson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / J	Severity:	S4 (Feature request)
Version:	Any	OS:	Any (Any)
Assigned to:	Alexander Soklakov	CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
Mark,

In anticipation of this feature, hoping that the driver will correctly identify which server mode is being used for the sake of correct PreparedStatement string escaping.

http://bugs.mysql.com/bug.php?id=6368 

Thanks,
ken

How to repeat:
n/a

Detection of NO_BACKSLASH_ESCAPES was implemented in c/J 3.1.7, Prepared statements fixes were introduced in several following 3.1 releases.

So this feature also presents in current driver version.

Added entry to 3.1.7 changelog:

Connector/J now supports the 'NO_BACKSLASH_ESCAPES' server SQL mode.