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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2012/10/02 02:32:08 UTC
[jira] [Updated] (DERBY-3102) Statements are not removed from the
cache, even when they are of no use, e.g. statements that reference a
dropped table.
[ https://issues.apache.org/jira/browse/DERBY-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamta A. Satoor updated DERBY-3102:
-----------------------------------
Urgency: Normal
Labels: derby_triage10_10 (was: )
> Statements are not removed from the cache, even when they are of no use, e.g. statements that reference a dropped table.
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3102
> URL: https://issues.apache.org/jira/browse/DERBY-3102
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.3.1.4
> Reporter: Kathey Marsden
> Priority: Minor
> Labels: derby_triage10_10
> Attachments: TestCache.java
>
>
> Dan pointed this out in DERBY-2344 and I thought it worthy of its own bug. The attached program shows the number of statements in the cache growing even though the table is dropped.
> [C:/kmarsden/repro/DERBY-2344] java TestCache
> number of cache entries: 5
> number of cache entries: 9
> number of cache entries: 13
> number of cache entries: 17
> number of cache entries: 21
> number of cache entries: 25
> number of cache entries: 29
> number of cache entries: 33
> number of cache entries: 37
> number of cache entries: 41
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira