db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2914) new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS, SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented
Date Tue, 04 Sep 2007 22:02:48 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524894
] 

Daniel John Debrunner commented on DERBY-2914:
----------------------------------------------

The syntax to call this procedure is:

CALL SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE()

The procedure has no parameters.

It empties the database wide statement cache of all compiled statements (plans).

> new stored procedures, SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS,
SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE() should get documented
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2914
>                 URL: https://issues.apache.org/jira/browse/DERBY-2914
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.3.1.4, 10.4.0.0
>            Reporter: Myrna van Lunteren
>            Assignee: Laura Stewart
>
> With DERBY-2772 and DERBY-2735 3 new procedures
> SYSCS_UTIL.SYSCS_SET_USER_ACCESS, SYSCS_UTIL.SYSCS_GET_USER_ACCESS and SYSCS_UTIL.SYSCS_EMPTY_STATEMENT_CACHE()
>  were created; they need to be documented in the reference manual.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message