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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/01/08 15:37:56 UTC

[jira] [Updated] (DERBY-6449) Analyze and possibly correct the suspicious addition of in-memory dependencies during statement execution

     [ https://issues.apache.org/jira/browse/DERBY-6449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-6449:
---------------------------------

    Summary: Analyze and possibly correct the suspicious addition of in-memory dependencies during statement execution  (was: Analyze and possible correct the suspicious addition of in-memory dependencies during statement execution)

> Analyze and possibly correct the suspicious addition of in-memory dependencies during statement execution
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6449
>                 URL: https://issues.apache.org/jira/browse/DERBY-6449
>             Project: Derby
>          Issue Type: Task
>          Components: SQL
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>
> During work on DERBY-6434, I was surprised to find that in-memory dependencies are added during statement execution. I had expected that the dependency graph would be completely built by the bind() phase. This issue is a place to record an analysis of the calls to DependencyManager.addDependency() made by the ConstantActions and to make any necessary changes.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)