Re: Backward compatibility of prepared statements broken in 3.1.6
Posted by: Jason Winnebeck
Date: February 11, 2005 11:15AM

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)?

Jason Winnebeck
Center for Integrated Manufacturing Studies
Rochester Institute of Technology, Rochester NY

Options: ReplyQuote


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


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.