[
https://issues.apache.org/jira/browse/DERBY-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590201#action_12590201
]
Knut Anders Hatlen commented on DERBY-3622:
-------------------------------------------
Thanks for picking this up, Kim. I think the description is correct. The
javadoc[1] for this procedure says that it is not guaranteed that the cache is
empty after the call. Is it worth mentioning that? By the way, if it's not
guaranteed to be empty, "all compiled statements" is probably a little too
strong. Perhaps it is more precise if we say "The
SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE stored procedure removes as many
compiled statements (plans) as possible from the database-wide statement cache."
[1]
http://db.apache.org/derby/javadoc/engine/org/apache/derby/catalog/SystemProcedures.html#SYSCS_EMPTY_STATEMENT_CACHE()
> SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE needs a better description in the
> reference manual
> -----------------------------------------------------------------------------------------
>
> Key: DERBY-3622
> URL: https://issues.apache.org/jira/browse/DERBY-3622
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.4.1.1
> Reporter: Knut Anders Hatlen
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-3622.diff, rrefemptystmtcache.html
>
>
> Currently, the reference manual describes the
> SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE system procedure like this[1]:
> > The SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE stored procedure is a useful
> > diagnostic tool.
> The description should state what the procedure does, not only that it's
> useful. (I'm not even sure it's true that it is a diagnostic tool.)
> [1] http://db.apache.org/derby/docs/dev/ref/rrefemptystmtcache.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
