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

John H. Embretsen commented on DERBY-2914:
------------------------------------------

Aha, so that's why my 10.3 doc build failed (see my previous comment). I was 
assuming there was something wrong with my environment, but gave up trying to 
debug the dita error messages... Lesson learned.

> 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
>             Fix For: 10.3.1.4
>
>         Attachments: derby2914_1.diff, derby2914_2.diff, derby2914_3.diff, 
> derby2914_4.diff, derby2914_5.diff, derby2914_6.diff, derby2914_7.diff, 
> index.html, rrefemptystmtcache.html, rrefemptystmtcache.html, 
> rrefgetuseraccess.html, rrefgetuseraccess.html, rrefgetuseraccess.html, 
> rrefgetuseraccess.html, rrefgetuseraccess.html, rrefgetuseraccess.html, 
> rrefgetuseraccess.html, rrefsetuseraccess.html, rrefsetuseraccess.html, 
> rrefsetuseraccess.html, rrefsetuseraccess.html, rrefsetuseraccess.html, 
> rrefsetuseraccess.html, rrefsetuseraccess.html
>
>
> 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.

Reply via email to