You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2009/04/27 15:14:30 UTC

[jira] Created: (DERBY-4190) Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual

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: 10.5.1.1
            Reporter: Knut Anders Hatlen
            Priority: Minor


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:
SELECT * FROM TABLE (SYSCS_DIAG.CONTAINED_ROLES(reader))

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.


[jira] Commented: (DERBY-4190) Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual

Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
    [ 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: 10.5.1.1
>            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:
> SELECT * FROM TABLE (SYSCS_DIAG.CONTAINED_ROLES(reader))
> 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.


[jira] Assigned: (DERBY-4190) Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual

Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton reassigned DERBY-4190:
--------------------------------------

    Assignee: Bryan Pendleton

> 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: 10.5.1.1
>            Reporter: Knut Anders Hatlen
>            Assignee: Bryan Pendleton
>            Priority: Minor
>
> 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:
> SELECT * FROM TABLE (SYSCS_DIAG.CONTAINED_ROLES(reader))
> 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.


[jira] Closed: (DERBY-4190) Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen closed DERBY-4190.
-------------------------------------


Verified fix in latest alpha manuals. Closing.

> 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: 10.5.1.1
>            Reporter: Knut Anders Hatlen
>            Assignee: Bryan Pendleton
>            Priority: Minor
>             Fix For: 10.6.0.0
>
>         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:
> SELECT * FROM TABLE (SYSCS_DIAG.CONTAINED_ROLES(reader))
> 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.


[jira] Resolved: (DERBY-4190) Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual

Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton resolved DERBY-4190.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.6.0.0

Thanks Kim and Dag for the reviews.

I changed 'reader' to 'READER' and <i>current_role</i> to CURRENT_ROLE
and submitted the change to the docs trunk as revision 835665.


> 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: 10.5.1.1
>            Reporter: Knut Anders Hatlen
>            Assignee: Bryan Pendleton
>            Priority: Minor
>             Fix For: 10.6.0.0
>
>         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:
> SELECT * FROM TABLE (SYSCS_DIAG.CONTAINED_ROLES(reader))
> 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.


[jira] Commented: (DERBY-4190) Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual

Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777213#action_12777213 ] 

Kim Haase commented on DERBY-4190:
----------------------------------

Thanks, Bryan! One more item: we typically say CURRENT_ROLE with no special font. It's actually a function.

> 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: 10.5.1.1
>            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:
> SELECT * FROM TABLE (SYSCS_DIAG.CONTAINED_ROLES(reader))
> 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.


[jira] Updated: (DERBY-4190) Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual

Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Pendleton updated DERBY-4190:
-----------------------------------

    Attachment: rrefsyscsdiagtables.html
                docs.diff

Attached is a patch proposal, and the resulting HTML page.

In addition to the changes suggested by Knut, I also added some text
and an example for the CURRENT_ROLE case.

I wasn't sure if the example should read 'reader' or 'READER'; are
role names generally upper case?

Please have a look at the revised doc and let me know any comments.


> 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: 10.5.1.1
>            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:
> SELECT * FROM TABLE (SYSCS_DIAG.CONTAINED_ROLES(reader))
> 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.


[jira] Commented: (DERBY-4190) Incorrect example for SYSCS_DIAG.CONTAINED_ROLES in the reference manual

Posted by "Dag H. Wanvik (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777180#action_12777180 ] 

Dag H. Wanvik commented on DERBY-4190:
--------------------------------------

Thanks for fixing this one, Bryan. +1 after the case change.


> 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: 10.5.1.1
>            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:
> SELECT * FROM TABLE (SYSCS_DIAG.CONTAINED_ROLES(reader))
> 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.