Return-Path: 
 <derby-commits-return-15801-apmail-db-derby-commits-archive=db.apache.org@db.apache.org>
X-Original-To: apmail-db-derby-commits-archive@www.apache.org
Delivered-To: apmail-db-derby-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A1B5FC405
	for <apmail-db-derby-commits-archive@www.apache.org>;
 Thu, 28 Jun 2012 20:33:01 +0000 (UTC)
Received: (qmail 75383 invoked by uid 500); 28 Jun 2012 20:33:01 -0000
Delivered-To: apmail-db-derby-commits-archive@db.apache.org
Received: (qmail 75321 invoked by uid 500); 28 Jun 2012 20:33:01 -0000
Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:derby-commits-help@db.apache.org>
list-unsubscribe: <mailto:derby-commits-unsubscribe@db.apache.org>
List-Post: <mailto:derby-commits@db.apache.org>
Reply-To: "Derby Development" <derby-dev@db.apache.org>
List-Id: <derby-commits.db.apache.org>
Delivered-To: mailing list derby-commits@db.apache.org
Received: (qmail 75314 invoked by uid 99); 28 Jun 2012 20:33:01 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jun 2012 20:33:01 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jun 2012 20:32:58 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
	by eris.apache.org (Postfix) with ESMTP id 1A95F2388A3D;
	Thu, 28 Jun 2012 20:32:36 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r1355150 -
 /db/derby/docs/branches/10.9/src/ref/rrefsyscsdiagtables.dita
Date: Thu, 28 Jun 2012 20:32:35 -0000
To: derby-commits@db.apache.org
From: chaase3@apache.org
X-Mailer: svnmailer-1.0.8-patched
Message-Id: <20120628203236.1A95F2388A3D@eris.apache.org>

Author: chaase3
Date: Thu Jun 28 20:32:34 2012
New Revision: 1355150

URL: http://svn.apache.org/viewvc?rev=1355150&view=rev
Log:
DERBY-5822  Document the new SQL standard behavior of the SPACE_TABLE vti

Merged DERBY-5822.diff to 10.9 docs branch from trunk revision 1355117.

Modified:
    db/derby/docs/branches/10.9/src/ref/rrefsyscsdiagtables.dita

Modified: db/derby/docs/branches/10.9/src/ref/rrefsyscsdiagtables.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.9/src/ref/rrefsyscsdiagtables.dita?rev=1355150&r1=1355149&r2=1355150&view=diff
==============================================================================
--- db/derby/docs/branches/10.9/src/ref/rrefsyscsdiagtables.dita (original)
+++ db/derby/docs/branches/10.9/src/ref/rrefsyscsdiagtables.dita Thu Jun 28 20:32:34 2012
@@ -182,10 +182,18 @@ to determine if space might be saved by 
 <p>All users can access this diagnostic table function, whether or not the
 database has authentication and SQL authorization enabled.</p>
 <p>To access the SYSCS_DIAG.SPACE_TABLE diagnostic table function, you must use
-the SQL table function syntax. This diagnostic table function takes two arguments,
-the <parmname>schemaName</parmname> and the <parmname>tableName</parmname>.
-The <parmname>tableName</parmname> argument is required. If you do not specify
-the <parmname>schemaName</parmname>, the current schema is used. </p>
+the SQL table function syntax. You can invoke the table function in the
+following ways:
+<ul>
+<li>If invoked with no arguments, the table function retrieves
+space information for all tables and indexes in the database.</li>
+<li>If invoked with one argument, a <parmname>tableName</parmname>, the table
+function retrieves information for the specified table in the current
+schema.</li>
+<li>If invoked with two arguments, a <parmname>schemaName</parmname> followed by
+a <parmname>tableName</parmname>, the table function retrieves information for
+the specified schema and table.</li>
+</ul></p>
 <p>The returned table has the columns shown in the following table.</p>
 <table frame="all">
 <title>Columns returned by the SYSCS_DIAG.SPACE_TABLE function</title>
@@ -254,16 +262,25 @@ the <parmname>schemaName</parmname>, the
 <entry colname="4">false</entry>
 <entry colname="5">The estimated space which could possibly be saved by compressing the conglomerate, in bytes.</entry>
 </row>
+<row>
+<entry colname="1">TABLEID</entry>
+<entry colname="2">CHAR</entry>
+<entry colname="3">36</entry>
+<entry colname="4">false</entry>
+<entry colname="5">The id of the table to which the conglomerate belongs. </entry>
+</row>
 </tbody>
 </tgroup>
 </table>
-<p>For
-example, use the following query to return the space usage for all of the
-user tables and indexes in the database: <codeblock>SELECT T2.*
-    FROM 
+<p>For example, use the following query to return the space usage for all of the
+user tables and indexes in the database:
+<codeblock>SELECT T2.*
+    FROM
         SYS.SYSTABLES systabs,
-        TABLE (SYSCS_DIAG.SPACE_TABLE(systabs.tablename)) AS T2
-    WHERE systabs.tabletype = 'T'</codeblock>where T2 is a user-specified
+        TABLE (SYSCS_DIAG.SPACE_TABLE()) AS T2
+    WHERE systabs.tabletype = 'T'
+    AND systabs.tableid = T2.tableid;</codeblock>
+where T2 is a user-specified
 table name that is any valid identifier. </p><p>Both the <parmname>schemaName</parmname> and
 the <parmname>tableName</parmname> arguments must be expressions whose data
 types map to Java strings. If the <parmname>schemaName</parmname> and the <parmname>tableName</parmname> are