[
https://issues.apache.org/jira/browse/DERBY-4680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918947#action_12918947
]
Dag H. Wanvik commented on DERBY-4680:
--------------------------------------
Thanks, Kim! This looks great now.
One more thing: in the rrefcallprocedure.dita, we now spell out what happens to
current schema and current role when running with definer's right. We are not
so explicit about what happens when invoking a routine with invoker's rights
(the default) and what happens on return.
Maybe, to be clear, we should add a sentence or two about that here, too. E.g.
"When a procedure with invoker's's rights is called, the current default
schema, current role is unchanged initially within the procedure.
Similarly, if SQL authorization mode is not enabled, the current default schema
is unchanged initially within the procedure.
When returning from the call, any changes made inside the procedure to default
current schema (and current role if relevant) are reset (popped)."
It also just struck me that the functions call documentation should also be
updated with definer's rights, so we should probably duplicate the information
in this section (replacing procedure with function) somwhere...?
> Add documentation for routines running with definer's rights
> ------------------------------------------------------------
>
> Key: DERBY-4680
> URL: https://issues.apache.org/jira/browse/DERBY-4680
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Reporter: Dag H. Wanvik
> Assignee: Kim Haase
> Fix For: 10.7.0.0
>
> Attachments: DERBY-4680-2.diff, DERBY-4680-2.stat, DERBY-4680-2.zip,
> DERBY-4680.diff, DERBY-4680.stat, DERBY-4680.zip
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
