You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Oyvind Bakksjo (JIRA)" <de...@db.apache.org> on 2005/09/20 16:08:29 UTC

[jira] Updated: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

     [ http://issues.apache.org/jira/browse/DERBY-579?page=all ]

Oyvind Bakksjo updated DERBY-579:
---------------------------------

    Attachment: DERBY-579.svn.status

> 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.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