[ http://issues.apache.org/jira/browse/DERBY-579?page=all ]
Oyvind Bakksjo updated DERBY-579:
---------------------------------
Attachment: DERBY-579.svn.diff
This patch fixes the bug as proposed by Dan Debrunner ("pass the timeout into
the execute method of
org.apache.derby.iapi.sql.PreparedStatement, not store it as a field in
GenericPreparedStatement.").
jdbcapi test has been run without errors. Currently running derbyall.
svn diff executed on revision 290453.
> Query timeout set for one statement may affect other statements with the same
> SQL string
> ----------------------------------------------------------------------------------------
>
> Key: DERBY-579
> URL: http://issues.apache.org/jira/browse/DERBY-579
> Project: Derby
> Type: Bug
> Components: SQL
> Reporter: Oyvind Bakksjo
> Assignee: Oyvind Bakksjo
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: DERBY-579.svn.diff, DERBY-579.svn.status
>
> The timeout is being set on the class GenericPreparedStatement, but this
> represents a statement plan and can be shared across multiple
> connections (through the statement cache). Thus if two connections
> execute the same statement with different timeouts, they will interfere
> with each other with the timeout values.
--
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
