db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3137) SQL roles: add catalog support
Date Wed, 30 Jan 2008 15:02:42 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564039#action_12564039

Dag H. Wanvik commented on DERBY-3137:

So, to clarify further, the following would be equivalent:

ps.setString(1, "\" SPACEADMIN \""); // Role CNF of SPACEADMIN (surrounded by spaces on each
ps.setString(1, " \" SPACEADMIN \"     "); // Role CNF of SPACEADMIN (surrounded by spaces
on each side).  TRIMable space in value string

I am OK with moving towards stricter adherence here; I'll make an update patch.

Thanks for the suggestion on reserving namespace. Since Derby uses SYS as a reserved schema
name, I guess the "SYS-" prefix is as good as any.
I'll add this to the specification and make an update patch.

> 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:
>         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.

View raw message