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-4190) Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual
Date Thu, 12 Nov 2009 20:42:41 GMT

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

Dag H. Wanvik commented on DERBY-4190:

When a role is created, the identifier is converted to upper case internally
unless it is a delimited identifier (as for other identifiers in Derby), so 'READER' would
be good in the example.

> Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual
> ------------------------------------------------------------------------
>                 Key: DERBY-4190
>                 URL: https://issues.apache.org/jira/browse/DERBY-4190
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Bryan Pendleton
>            Priority: Minor
>         Attachments: docs.diff, rrefsyscsdiagtables.html
> The example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual does not work.
> http://db.apache.org/derby/docs/dev/ref/rrefsyscsdiagtables.html
> The example looks like this:
> There are two problems:
> 1) the table needs an alias (for instance, append AS T1), otherwise this error is raised:
> ERROR 42X01: Syntax error: Encountered "<EOF>" at line 1, column 56.
> Issue the 'help' command for general information on IJ command syntax.
> Any unrecognized commands are treated as potential SQL commands and executed directly.
> Consult your DBMS server reference documentation for details of the SQL syntax supported
by your server.
> 2) the name of the role should be a string (needs single quotes), not an identifier,
otherwise this error is raised:
> ERROR 42X04: Column 'READER' is either not in any table in the FROM list or appears within
a join specification and is outside the scope of the join specification or appears in a HAVING
clause and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE  statement then
'READER' is not a column in the target table.

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

View raw message