db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1581) BasicDependencyManager re-loads the Provider multiple times from the DataDictionary when loading the stored dependencies for the Provider.
Date Mon, 24 Jul 2006 23:11:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1581?page=all ]

Daniel John Debrunner updated DERBY-1581:
-----------------------------------------

    Attachment: derby1581_draft.txt

Proposed patch - only had limited testing so far. Will test using derbyall

> BasicDependencyManager re-loads the Provider multiple times from the DataDictionary when
loading the stored dependencies for the Provider.
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1581
>                 URL: http://issues.apache.org/jira/browse/DERBY-1581
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>            Priority: Minor
>             Fix For: 10.2.0.0
>
>         Attachments: derby1581_draft.txt
>
>
> From work on DERBY-1593 & DERBY-1330  it was discovered the DependencyMangerImpl
 loaded the same Provier multiple times from the DataDictionary while loading the stored dependecies
and converting them to an in-memory form.  There is no need to load the Provider from the
 DataDictionary because it is passed into the DependencyManger.invalidateFor call that results
in the loading of the stored dependencies.

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

        

Mime
View raw message