Bug #69077 | Server-side PreparedStatement restrictions don't reflect current capabilities | ||
---|---|---|---|
Submitted: | 26 Apr 2013 5:43 | ||
Reporter: | Todd Farmer (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 5.1.24 | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
[26 Apr 2013 5:43]
Todd Farmer
[6 May 2013 21:36]
Jess Balint
According to the docs, DO, SET, CREATE TABLE are supported in SSPS going back to 4.1, and CALL since 5.0 (when SPs were introduced)
[7 May 2013 23:17]
Todd Farmer
Changing canHandleAsServerPreparedStatementNoCache() to always return true produces no meaningful regressions in StatementRegressionTest. This is because emulateUnsupportedPstmts defaults to true, which handles *any* SQLException in the attempt to prepare a statement (not just error 1295) as a trigger to fail to emulated, client-side prepared statements.