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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2012/06/19 19:42:43 UTC
[jira] [Created] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Rick Hillegas created DERBY-5822:
------------------------------------
Summary: Document the new SQL standard behavior of the SPACE_TABLE vti
Key: DERBY-5822
URL: https://issues.apache.org/jira/browse/DERBY-5822
Project: Derby
Issue Type: Bug
Components: Documentation
Affects Versions: 10.10.0.0
Reporter: Rick Hillegas
We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
1) Describe the new TABLEID column which was added to SPACE_TABLE:
Column Name: TABLEID
Type: CHAR
Length: 36
Nullable: False
Contents: The id of the table which the conglomerate belongs to.
2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
select t2.*
from
sys.systables systabs,
table (syscs_diag.space_table()) as t2
where systabs.tabletype = 'T'
and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-5822:
-----------------------------
Issue & fix info: Patch Available
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-5822.diff, rrefsyscsdiagtables.html
>
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-5822:
-----------------------------
Attachment: DERBY-5822.diff
rrefsyscsdiagtables.html
Attaching DERBY-5822.diff and rrefsyscsdiagtables.html, with changes to rrefsyscsdiagtables.dita ("SYSCS_DIAG diagnostic tables and functions").
Thanks for the very clear description, Rick! Please let me know what changes are needed.
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-5822.diff, rrefsyscsdiagtables.html
>
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398701#comment-13398701 ]
Rick Hillegas commented on DERBY-5822:
--------------------------------------
Hi Kim. Yes, we should fix the documentation in 10.9 and 10.8 after I port the fixes to those branches.
Hi Kathey. Yes, the old syntax still works. We just want to steer users toward standard syntax which will work in more cases.
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403389#comment-13403389 ]
Kim Haase commented on DERBY-5822:
----------------------------------
Thanks, Rick! Committed patch DERBY-5822.diff to documentation trunk at revision 1355117.
It appears that the fix for DERBY-5554 has been ported to the 10.9 and 10.8 branches, but the issue has not yet been resolved. Is it okay to port the doc fix to the branches as well?
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-5822.diff, rrefsyscsdiagtables.html
>
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403421#comment-13403421 ]
Rick Hillegas commented on DERBY-5822:
--------------------------------------
Thanks, Kim. Please port the doc fix to 10.9 and 10.8. I have added a comment to DERBY-5554, explaining why I have left that issue open. Thanks.
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-5822.diff, rrefsyscsdiagtables.html
>
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398640#comment-13398640 ]
Kim Haase commented on DERBY-5822:
----------------------------------
If DERBY-5554 is ported to 10.9 and 10.8, I am assuming the revised documentation should also be committed to those branches when it is completed. Let me know if this assumption is unfounded.
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-5822.
------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
10.9.1.1
10.8.2.3
Issue & fix info: (was: Patch Available)
Thanks very much, Rick.
Merged DERBY-5822.diff to 10.9 doc branch at revision 1355150.
Merged DERBY-5822.diff to 10.8 doc branch at revision 1355154.
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Fix For: 10.8.2.3, 10.9.1.1, 10.10.0.0
>
> Attachments: DERBY-5822.diff, rrefsyscsdiagtables.html
>
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398690#comment-13398690 ]
Kathey Marsden commented on DERBY-5822:
---------------------------------------
Am I correct that the old example spacetable syntax will still execute but is just needs to be discouraged?
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400761#comment-13400761 ]
Rick Hillegas commented on DERBY-5822:
--------------------------------------
Thanks, Kim. The patch looks good to me. +1
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-5822.diff, rrefsyscsdiagtables.html
>
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DERBY-5822) Document the new SQL standard
behavior of the SPACE_TABLE vti
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-5822:
--------------------------------
Assignee: Kim Haase
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (DERBY-5822) Document the new SQL standard behavior
of the SPACE_TABLE vti
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase closed DERBY-5822.
----------------------------
Closing, since changes have appeared in Latest Alpha Manuals (as well as 10.9 and 10.8).
> Document the new SQL standard behavior of the SPACE_TABLE vti
> -------------------------------------------------------------
>
> Key: DERBY-5822
> URL: https://issues.apache.org/jira/browse/DERBY-5822
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Fix For: 10.8.2.3, 10.9.1.1, 10.10.0.0
>
> Attachments: DERBY-5822.diff, rrefsyscsdiagtables.html
>
>
> We will want to improve the Reference Guide section on the SPACE_TABLE vti after we commit the derby-5554-02-aa-0argConstructor.diff attached to DERBY-5554. We will want to make the following changes:
> 1) Describe the new TABLEID column which was added to SPACE_TABLE:
> Column Name: TABLEID
> Type: CHAR
> Length: 36
> Nullable: False
> Contents: The id of the table which the conglomerate belongs to.
> 2) Describe the additional no-arg constructor for this vti. There are now 3 ways to construct this vti:
> i) No args. This is the new constructor which needs to be described. When the vti is invoked with no arguments, it retrieves space information for all tables and indexes in the database.
> ii) One argument. This constructor is already described. If the vti is invoked with one string argument, then that argument is the name of a table in the current schema.
> iii) Two arguments. This constructor is already described also. When the vti is invoked with two string arguments, the first argument is a schema name and the second argument is a table name.
> 3) Replace the first SPACE_TABLE example. That example uses Derby-specific syntax which falls outside the SQL Standard. Showcasing non-standard syntax encourages users to try out other non-standard syntax, giving rise to bugs like DERBY-5554. We should showcase the following standard syntax instead:
> select t2.*
> from
> sys.systables systabs,
> table (syscs_diag.space_table()) as t2
> where systabs.tabletype = 'T'
> and systabs.tableid = t2.tableid;
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira