[
https://issues.apache.org/jira/browse/DERBY-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564270#action_12564270
]
Dag H. Wanvik commented on DERBY-3137:
--------------------------------------
Re: identifiers vs CNF: Indeed confusing. I think I was under the impression
the <values specification> would yield a CNF value, which is
why I added the extra syntax for using identifers also, like SET SCHEMA does.
This is why I was wary of the TRIM I think; a CNF value would not have any
protective text quotes around it.
One interpretation of 5.2 SR 24 could be that CNF values is only ever available
as a string value in queries against the system tables? It would then behoove
the app to take into account when comparing, but perhaps it would simplify
things on the whole?
Or maybe the standard intends for a comparison of CURRENT_ROLE against
information schemas to be an identifer comparison, not a string comparison.. in
which case the standard is inconsistent I think.
> SQL roles: add catalog support
> ------------------------------
>
> Key: DERBY-3137
> URL: https://issues.apache.org/jira/browse/DERBY-3137
> Project: Derby
> Issue Type: New Feature
> Components: Security, SQL
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Fix For: 10.4.0.0
>
> Attachments: DERBY-3137-2.diff, DERBY-3137-2.stat, DERBY-3137-2.txt,
> DERBY-3137-uuid.diff, DERBY-3137-uuid.stat, DERBY-3137.diff, DERBY-3137.diff,
> DERBY-3137.stat, DERBY-3137.txt
>
>
> As a next step after adding support for the roles syntax, I intend to
> make a patch which implements catalog support for roles,
> cf. SYS.SYSROLES described in the specification (attached to
> DERBY-2207). Also the patch should tie this support up to the parser
> support, so the role statements can be executed. Any privileges
> granted to roles would still have no effect at run-time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
