Re: Backward compatibility of prepared statements broken in 3.1.6
Posted by: Mark Matthews
Date: February 11, 2005 11:31AM

Jason Winnebeck wrote:
> Couldn't you just revert to the old client-side
> behavior when the server protocol doesn't support
> it? An extremely brief view of the code via
> various stack traces I've seen from connections
> hints strongly that you have an abstract type of
> PS then you have concrete definitions like
> ServerPreparedStatement. Couldn't you just have
> code that says return ServerPS when supported,
> else return a ClientPS (or whatever the class is
> called)?


Already pushed into the codeline for 3.1.7 (from the CHANGES file):

"By default, the driver now scans SQL you are preparing via all variants
of Connection.prepareStatement() to determine if it is a supported
type of statement to prepare on the server side, and if it is not
supported by the server, it instead prepares it as a client-side emulated
prepared statement (BUG#4718). You can disable this by passing
'emulateUnsupportedPstmts=false' in your JDBC URL."

This is in the nightly builds available at if you want to test it before official release.


Mark Matthews
Consulting Member Technical Staff - MySQL Enterprise Tools

Options: ReplyQuote

Written By
Re: Backward compatibility of prepared statements broken in 3.1.6
February 11, 2005 11:31AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.