[ http://issues.apache.org/jira/browse/DERBY-1227?page=comments#action_12422505 ] Sunitha Kambhampati commented on DERBY-1227: --------------------------------------------
After applying the patch and the merge command to backport to 10.1, here is the svn stat info: M java\engine\org\apache\derby\impl\jdbc\EmbedPreparedStatement.java M java\engine\org\apache\derby\impl\jdbc\EmbedParameterSetMetaData.java M java\engine\org\apache\derby\iapi\jdbc\BrokeredPreparedStatement.java A + java\engine\org\apache\derby\iapi\jdbc\EngineParameterMetaData.java A + java\engine\org\apache\derby\iapi\jdbc\EnginePreparedStatement.java M java\drda\org\apache\derby\impl\drda\DRDAStatement.java M java\drda\org\apache\derby\impl\drda\DRDAConnThread.java > Network Server should not use the underlying embedded prepared statement when > accessing a BrokeredPreparedStatement > ------------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1227 > URL: http://issues.apache.org/jira/browse/DERBY-1227 > Project: Derby > Issue Type: Bug > Components: Network Server > Affects Versions: 10.1.2.1 > Reporter: Kathey Marsden > Assigned To: Sunitha Kambhampati > Fix For: 10.2.0.0 > > Attachments: 10.1_p1_derby1227.diff.txt > > > Network Server should not use the underlying embedded > Prepared statement when accessing a BrokeredPreparedStatement. > In DERBY-1025 Dan pointed out this code which while not related to DERBY-1025 > does appear to be a problem. Here is his comment regarding this code in > DRDAStatement: > /** > * Get prepared statement > * > * @return prepared statement > */ > protected PreparedStatement getPreparedStatement() throws SQLException > { > if (ps instanceof BrokeredPreparedStatement) > return (PreparedStatement)( > ((BrokeredPreparedStatement) ps).getStatement()); > else > return ps; > } > This code, for some unknown reason due to lack of comments, is getting the > underlying embedded statement > from a BrokeredPreparedStatement. This should not be allowed, the > BrokeredStatement wrappers are there to > hide the embedded statement object as it can change under the covers of the > wrapper. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
