db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chaa...@apache.org
Subject svn commit: r733908 - /db/derby/docs/trunk/src/ref/
Date Mon, 12 Jan 2009 21:36:59 GMT
Author: chaase3
Date: Mon Jan 12 13:36:51 2009
New Revision: 733908

URL: http://svn.apache.org/viewvc?rev=733908&view=rev
Log:
DERBY-3959: Reference Manual needs information on generated columns

This patch provides information on the new generated columns feature, adding one new topic
to the Reference Manual and updating 9 more.

Patch: DERBY-3959-2.diff

Added:
    db/derby/docs/trunk/src/ref/rrefsqljgenerationclause.dita   (with props)
Modified:
    db/derby/docs/trunk/src/ref/refderby.ditamap
    db/derby/docs/trunk/src/ref/rrefcreatefunctionstatement.dita
    db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita
    db/derby/docs/trunk/src/ref/rrefdropfunctionstatement.dita
    db/derby/docs/trunk/src/ref/rrefsqlj26498.dita
    db/derby/docs/trunk/src/ref/rrefsqlj30540.dita
    db/derby/docs/trunk/src/ref/rrefsqlj40774.dita
    db/derby/docs/trunk/src/ref/rrefsqlj43125.dita
    db/derby/docs/trunk/src/ref/rrefsqlj81859.dita
    db/derby/docs/trunk/src/ref/rrefsqljrenamecolumnstatement.dita

Modified: db/derby/docs/trunk/src/ref/refderby.ditamap
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/refderby.ditamap?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/refderby.ditamap (original)
+++ db/derby/docs/trunk/src/ref/refderby.ditamap Mon Jan 12 13:36:51 2009
@@ -163,6 +163,8 @@
 </topicref>
 <topicref href="rrefsqlj37836.dita" navtitle="generated-column-spec" toc="no">
 </topicref>
+<topicref href="rrefsqljgenerationclause.dita" navtitle="generation-clause" toc="no">
+</topicref>
 </topicref>
 <topicref collection-type="family" href="rrefsqlj43125.dita" navtitle="CREATE TRIGGER
statement">
 <topicref href="rrefsqlj89752.dita" navtitle="ReferencingClause" toc="no">

Modified: db/derby/docs/trunk/src/ref/rrefcreatefunctionstatement.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefcreatefunctionstatement.dita?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefcreatefunctionstatement.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefcreatefunctionstatement.dita Mon Jan 12 13:36:51 2009
@@ -86,6 +86,7 @@
 
 <example id="rrefcrprofunctionelement"> <title>FunctionElement</title><codeblock><b>
{
 | LANGUAGE { JAVA }
+| <xref href="rrefcreatefunctionstatement.dita#rrefcreatefunctionstatement/rrefcrfunctiondetchar">DeterministicCharacteristic</xref>
 | EXTERNAL NAME <i>string</i>
 | PARAMETER STYLE <xref href="rrefcreatefunctionstatement.dita#rrefcreatefunctionstatement/rrefcrfunctionparameterstyle">ParameterStyle</xref>
 | { NO SQL | CONTAINS SQL | READS SQL DATA }
@@ -97,7 +98,14 @@
 the Java method to be called when the function is executed, and takes the
 following form: <codeblock>class_name.method_name</codeblock>The External
 Name cannot have any extraneous spaces.</p></section>
-
+<section id="rrefcrfunctiondetchar"><title>DeterministicCharacteristic</title>
+<codeblock><b>DETERMINISTIC | NOT DETERMINISTIC</b></codeblock>
+<p>Declares that the function is deterministic, meaning that with the same
+set of input values, it always computes the same result. The default is NOT
+DETERMINISTIC. <ph conref="../conrefs.dita#prod/productshortname"></ph> cannot
+recognize whether an operation is actually deterministic, so you must take care
+to specify the <codeph>DeterministicCharacteristic</codeph> correctly.</p>
+</section>
 <example id="rrefcrfunctionparameterstyle"><title>ParameterStyle</title>
 <codeblock><b>JAVA | DERBY_JDBC_RESULT_SET</b></codeblock></example>
 <section><p>The function will

Modified: db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita Mon Jan 12 13:36:51 2009
@@ -55,6 +55,7 @@
 <example id="rrefcrproprocedureelement"> <title>ProcedureElement</title><codeblock><b>
{ 
 | [ DYNAMIC ] RESULT SETS <i><xref href="rrefsqlj10696.dita#rrefsqlj10696">INTEGER</xref></i>
 | LANGUAGE { JAVA }
+| <xref href="rrefcreateprocedurestatement.dita#rrefcreateprocedurestatement/rrefcrproceduredetchar">DeterministicCharacteristic</xref>
 | EXTERNAL NAME <i>string</i>
 | PARAMETER STYLE JAVA
 | { NO SQL | MODIFIES SQL DATA | CONTAINS SQL | READS SQL DATA }
@@ -69,6 +70,14 @@
 the Java method to be called when the procedure is executed, and takes the
 following form: <codeblock>class_name.method_name</codeblock>The External
 Name cannot have any extraneous spaces.</p></section>
+<section id="rrefcrproceduredetchar"><title>DeterministicCharacteristic</title>
+<codeblock><b>DETERMINISTIC | NOT DETERMINISTIC</b></codeblock>
+<p>Declares that the procedure is deterministic, meaning that with the same
+set of input values, it always computes the same result. The default is NOT
+DETERMINISTIC. <ph conref="../conrefs.dita#prod/productshortname"></ph> cannot
+recognize whether an operation is actually deterministic, so you must take care
+to specify the <codeph>DeterministicCharacteristic</codeph> correctly. </p>
+</section>
 <section><title>PARAMETER STYLE</title> <p><b>JAVA</b>
- The procedure will
 use a parameter-passing convention that conforms to the Java language and
 SQL Routines specification. INOUT and OUT parameters will be passed as single

Modified: db/derby/docs/trunk/src/ref/rrefdropfunctionstatement.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefdropfunctionstatement.dita?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefdropfunctionstatement.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefdropfunctionstatement.dita Mon Jan 12 13:36:51 2009
@@ -24,10 +24,18 @@
 <section><title>Syntax</title> <codeblock><b>DROP FUNCTION
<i>function-name</i></b></codeblock> <p>Identifies
 the particular function to be dropped, and is valid only if there is exactly
 one function instance with the <i>function-name</i> in the schema. The identified
-function can have any number of parameters defined for it. If no function
-with the indicated name in the named or implied schema, an error (SQLSTATE
-42704) will occur. An error will also occur if there is more than one specific
-instance of the function in the named or implied schema.</p></section>
+function can have any number of parameters defined for it.</p>
+<p>An error will occur in any of the following circumstances:</p>
+<ul>
+<li>If no function with the indicated name exists in the named or implied schema
+(the error is SQLSTATE 42704)</li>
+<li>If there is more than one specific instance of the function in the named or
+implied schema</li>
+<li>If you try to drop a user-defined function that is invoked in the
+<i>generation-clause</i> of a generated column</li>
+<li>If you try to drop a user-defined function that is invoked in a view</li>
+</ul>
+</section>
 </refbody>
 </reference>
 

Modified: db/derby/docs/trunk/src/ref/rrefsqlj26498.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqlj26498.dita?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqlj26498.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqlj26498.dita Mon Jan 12 13:36:51 2009
@@ -45,7 +45,12 @@
 or the select statement did not include a FOR UPDATE clause, all columns may be updated.</p>

 <p>Specifying
 DEFAULT for the update value sets the value of the column to the default defined
-for that table.</p> </refsyn>
+for that table.</p>
+<p>The DEFAULT literal is the only value which you can directly assign to a
+generated column. Whenever you alter the value of a column referenced by the
+<i>generation-clause</i> of a generated column,
+<ph conref="../conrefs.dita#prod/productshortname"></ph> recalculates the value
+of the generated column.</p> </refsyn>
 <example><title>Example</title> <codeblock><b><ph>--
All the employees except the manager of
 -- department (WORKDEPT) 'E21' have been temporarily reassigned. 
 -- Indicate this by changing their job (JOB) to NULL and their pay

Modified: db/derby/docs/trunk/src/ref/rrefsqlj30540.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqlj30540.dita?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqlj30540.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqlj30540.dita Mon Jan 12 13:36:51 2009
@@ -20,13 +20,21 @@
 <reference id="rrefsqlj30540" xml:lang="en-us">
 <title>column-definition</title>
 <refbody>
-<example> <codeblock><b><i><xref href="rrefsimplecolumnname.dita#rrefsimplecolumnname">Simple-column-Name</xref></i>
<i>DataType</i>
+<example> <codeblock><b><i><xref href="rrefsimplecolumnname.dita#rrefsimplecolumnname">Simple-column-Name</xref></i>
[ <i>DataType</i> ]
     [ <i><xref href="rrefsqlj16095.dita#rrefsqlj16095">Column-level-constraint</xref></i>
]*
     [ [ WITH ] DEFAULT <varname>DefaultConstantExpression</varname>
-       |<i><xref href="rrefsqlj37836.dita#rrefsqlj37836">generated-column-spec</xref></i>
]
+       | <i><xref href="rrefsqlj37836.dita#rrefsqlj37836">generated-column-spec</xref></i>

+       | <i><xref href="rrefsqljgenerationclause.dita#rrefsqljgenerationclause">generation-clause</xref></i>

+    ]
     [ <i><xref href="rrefsqlj16095.dita#rrefsqlj16095">Column-level-constraint</xref></i>
]*
 </b></codeblock></example>
-<section><p>The syntax of <i>DataType</i> is described in <xref
href="crefsqlj31068.dita#crefsqlj31068"></xref>.</p><p>The
+<section><p>The syntax of <i>DataType</i> is described in
+<xref href="crefsqlj31068.dita#crefsqlj31068"></xref>. The <i>DataType</i>
can
+be omitted only if you specify a <i>generation-clause</i>. If you omit the
+<i>DataType</i>, the type of the generated column is the type of the
+<i>generation-clause</i>. If you specify both a <i>DataType</i> and
a
+<i>generation-clause</i>, the type of the <i>generation-clause</i>
must be
+assignable to <i>DataType</i>.</p><p>The
 syntaxes of <i><xref href="rrefsqlj16095.dita#rrefsqlj16095">Column-level-constraint</xref></i>
and <i><xref
 href="rrefsqlj42154.dita#rrefsqlj42154">Table-level constraint</xref></i>
are described in <xref
 href="rrefsqlj13590.dita#rrefsqlj13590"></xref>.</p></section>

Modified: db/derby/docs/trunk/src/ref/rrefsqlj40774.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqlj40774.dita?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqlj40774.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqlj40774.dita Mon Jan 12 13:36:51 2009
@@ -27,7 +27,10 @@
 <section> <p><indexterm>Read-write VTIs<indexterm>and INSERTs</indexterm></indexterm>An
 INSERT statement creates a row or rows and stores them in the named table.
 The number of values assigned in an INSERT statement must be the same as the
-number of specified or implied columns.</p></section>
+number of specified or implied columns.</p>
+<p>Whenever you insert into a table which has generated columns,
+<ph conref="../conrefs.dita#prod/productshortname"></ph> calculates the values
+of those columns.</p></section>
 <refsyn><title>Syntax</title> <codeblock><b>INSERT INTO table-Name
     [ (<i><xref href="rrefsimplecolumnname.dita#rrefsimplecolumnname">Simple-column-Name</xref></i>
[ , <i><xref
 href="rrefsimplecolumnname.dita#rrefsimplecolumnname">Simple-column-Name</xref></i>]*
) ]
@@ -39,7 +42,9 @@
 column's default value into the column. Another way to insert the default
 value into the column is to omit the column from the column list and only
 insert values into other columns in the table. For more information see <xref
-href="rrefsqlj11277.dita#rrefsqlj11277">VALUES Expression</xref>.</p></li>
+href="rrefsqlj11277.dita#rrefsqlj11277">VALUES Expression</xref>.</p>
+<p>The DEFAULT literal is the only value which you can directly
+insert into a generated column.</p></li>
 <li>UNION expressions</li>
 </ul></p> <p>For more information about Query, see <xref href="rrefsqlj21571.dita#rrefsqlj21571"></xref>.</p>
</refsyn>
 <example> <codeblock><b>INSERT INTO COUNTRIES

Modified: db/derby/docs/trunk/src/ref/rrefsqlj43125.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqlj43125.dita?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqlj43125.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqlj43125.dita Mon Jan 12 13:36:51 2009
@@ -136,6 +136,8 @@
 <li>Before triggers cannot have INSERT, UPDATE or DELETE statements as their
 action.</li>
 <li>Before triggers cannot call procedures that modify SQL data as their action.</li>
+<li>The NEW variable of a Before trigger cannot reference a generated column.
+</li>
 </ul></p><p>The triggered-SQL-statement can reference database objects
other
 than the table upon which the trigger is declared. If any of these database
 objects is dropped, the trigger is invalidated. If the trigger cannot be successfully

Modified: db/derby/docs/trunk/src/ref/rrefsqlj81859.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqlj81859.dita?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqlj81859.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqlj81859.dita Mon Jan 12 13:36:51 2009
@@ -53,9 +53,21 @@
     LOCKSIZE { ROW | TABLE }
 }</b></codeblock></section>
 <example id="rrefaltercolumndef"> <title>column-definition</title><codeblock><b><i><xref
-href="rrefsimplecolumnname.dita#rrefsimplecolumnname">Simple-column-Name</xref></i>
<i>DataType</i>
+href="rrefsimplecolumnname.dita#rrefsimplecolumnname">Simple-column-Name</xref></i>
[ <i>DataType</i> ]
 [ <i><xref href="rrefsqlj16095.dita#rrefsqlj16095">Column-level-constraint</xref></i>
]*
-[ [ WITH ] DEFAULT <varname>DefaultConstantExpression</varname> ]</b></codeblock>
+[ [ WITH ] DEFAULT <varname>DefaultConstantExpression</varname>
+  | <i><xref href="rrefsqljgenerationclause.dita#rrefsqljgenerationclause">generation-clause</xref></i>
+]</b></codeblock>
+<p>The syntax for the <i>column-definition</i> for a new column is a subset
of
+the syntax for a column in a
+<xref href="rrefsqlj24513.dita#rrefsqlj24513">CREATE TABLE statement</xref>.</p>
+<p>The syntax of <i>DataType</i> is described in
+<xref href="crefsqlj31068.dita#crefsqlj31068"></xref>. The <i>DataType</i>
can
+be omitted only if you specify a <i>generation-clause</i>. If you omit the
+<i>DataType</i>, the type of the generated column is the type of the
+<i>generation-clause</i>. If you specify both a <i>DataType</i> and
a
+<i>generation-clause</i>, the type of the <i>generation-clause</i>
must be
+assignable to <i>DataType</i>.</p>
 <p>For details on <varname>DefaultConstantExpression</varname>, see 
 <xref href="rrefsqlj30540.dita#sqlj64478">Column default</xref>.</p></example>
 <example id="rrefsqlj37860"><title>column-alteration</title><codeblock><b><i>column-Name</i>
SET DATA TYPE VARCHAR(integer) |
@@ -91,10 +103,15 @@
 with RESTART WITH 6:<codeblock><b>ALTER TABLE tauto ALTER COLUMN i RESTART WITH
6</b></codeblock></p><p>ALTER
 TABLE does not affect any view that references the table being altered. This
 includes views that have an "*" in their SELECT list. You must drop and re-create
-those views if you wish them to return the new columns.</p></section>
+those views if you wish them to return the new columns.</p>
+<p><ph conref="../conrefs.dita#prod/productshortname"></ph> raises an error
if
+you try to change the <i>DataType</i> of a generated column to a type which is
+not assignable from the type of the <i>generation-clause</i>.
+<ph conref="../conrefs.dita#prod/productshortname"></ph> also raises an error
if
+you try to add a DEFAULT clause to a generated column.</p></section>
 <section><title>Adding columns</title><p>The syntax for the <i><xref
href="rrefsqlj81859.dita#rrefsqlj81859/rrefaltercolumndef">column-definition</xref
-></i> for a new column is the same as for a column in a CREATE TABLE statement.
-This means that a column constraint can be placed on the new column within
+></i> for a new column is almost the same as for a column in a CREATE TABLE
+statement. This syntax allows a column constraint to be placed on the new column within
 the ALTER TABLE ADD COLUMN statement. However, a column with a NOT NULL constraint
 can be added to an existing table if you give a default value; otherwise,
 an exception is thrown when the ALTER TABLE statement is executed. </p><p>Just
@@ -104,7 +121,10 @@
 trigger without an explicit column list, adding a column to that table in
 effect adds that column to the implicit update column list upon which the
 trigger is defined, and all references to transition variables are invalidated
-so that they pick up the new column.</note></section>
+so that they pick up the new column.</note>
+<p>If you add a generated column to a table, 
+<ph conref="../conrefs.dita#prod/productshortname"></ph> computes the generated
+values for all existing rows in the table.</p></section>
 <section><title>Adding constraints</title><p>ALTER TABLE ADD CONSTRAINT
adds
 a table-level constraint to an existing table. Any supported table-level constraint
 type can be added via ALTER TABLE. The following limitations exist on adding
@@ -141,14 +161,18 @@
 these types of objects depends on the column being dropped, DROP COLUMN
 RESTRICT will reject the statement.</p>
 <p>
-You may not drop the last (only) column in a table.</p>
+<ph conref="../conrefs.dita#prod/productshortname"></ph> also raises an error
if
+you specify RESTRICT when you drop a column referenced by the
+<i>generation-clause</i> of a generated column. However, if you specify CASCADE,
+the generated column is also dropped with CASCADE semantics.</p>
 <p>
-DROP COLUMN is not allowed if sqlAuthorization is true (see DERBY-1909).</p>
+You may not drop the last (only) column in a table.</p>
 <p>
 CASCADE/RESTRICT doesn't consider whether the column being dropped is used
 in any indexes. When a column is dropped, it is removed from any indexes
 which contain it. If that column was the only column in the index, the
-entire index is dropped.</p></section>
+entire index is dropped.</p>
+</section>
 <section><title>Dropping constraints</title><p>ALTER TABLE DROP CONSTRAINT
 drops a constraint on an existing table. To drop an unnamed constraint, you
 must specify the generated constraint name stored in <i>SYS.SYSCONSTRAINTS</i>
as

Added: db/derby/docs/trunk/src/ref/rrefsqljgenerationclause.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqljgenerationclause.dita?rev=733908&view=auto
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqljgenerationclause.dita (added)
+++ db/derby/docs/trunk/src/ref/rrefsqljgenerationclause.dita Mon Jan 12 13:36:51 2009
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
+ "../dtd/reference.dtd">
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+<reference id="rrefsqljgenerationclause" xml:lang="en-us">
+<title>generation-clause</title>
+<refbody>
+<example>
+<codeblock><b>GENERATED ALWAYS AS ( <i>value-expression</i> )</b></codeblock>
+<p>A <i>value-expression</i> is an <i>Expression</i> that resolves
to a single
+value, with some limitations that are described here. See
+<xref href="rrefsqlj19433.dita#rrefsqlj19433"></xref> for more information
+about <i>Expression</i>s.
+</p></example>
+<section><title>References</title>
+<p>The <i>generation-clause</i> may reference other non-generated columns
in
+the table, but it must not reference any generated column. The
+<i>generation-clause</i> must not reference a column in another table.</p>
+</section>
+<section><title>Functions</title>
+<p>The <i>generation-clause</i> may invoke user-coded functions, if the
+functions meet the following requirements:</p>
+<ul>
+<li>The functions must not read or write SQL data.</li>
+<li>The functions must have been declared DETERMINISTIC.</li>
+<li>The functions must not invoke any of the following possibly
+non-deterministic system functions:
+<ul>
+<li>CURRENT_DATE</li>
+<li>CURRENT_TIME</li>
+<li>CURRENT_TIMESTAMP</li>
+<li>CURRENT_USER</li>
+<li>CURRENT_ROLE</li>
+<li>CURRENT SCHEMA</li>
+<li>CURRENT SQLID</li>
+<li>SESSION_USER</li>
+</ul>
+</li>
+</ul>
+</section>
+<section><title>Subqueries</title>
+<p>The <i>generation-clause</i> must not include subqueries.</p>
+</section>
+<section><title>Foreign keys</title>
+<p>If the generated column is part of a foreign key that references another
+table, the referential action must not specify SET NULL or SET DEFAULT, and the
+update rule must not specify ON UPDATE CASCADE.</p>
+</section>
+<example><title>Example</title>
+<codeblock><b>CREATE TABLE employee
+(
+  employeeID           int,
+  name                 varchar( 50 ),
+  caseInsensitiveName  GENERATED ALWAYS AS( UPPER( name ) )
+);
+CREATE INDEX caseInsensitiveEmployeeName ON employee( caseInsensitiveName );
+</b></codeblock>
+</example>
+</refbody>
+</reference>

Propchange: db/derby/docs/trunk/src/ref/rrefsqljgenerationclause.dita
------------------------------------------------------------------------------
    svn:eol-style = native

Modified: db/derby/docs/trunk/src/ref/rrefsqljrenamecolumnstatement.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqljrenamecolumnstatement.dita?rev=733908&r1=733907&r2=733908&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqljrenamecolumnstatement.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqljrenamecolumnstatement.dita Mon Jan 12 13:36:51 2009
@@ -55,11 +55,10 @@
 </b></codeblock></p>
 </example>
 <section><title>Usage notes</title>
-<note id="restriction">If there is a view, trigger, check constraint, or
-foreign key constraint that references the column, attempts to rename it
-will generate an error.
-</note>
-<note id="restriction">The RENAME COLUMN statement
+<note type="restriction">If a view, trigger, check constraint, foreign key
+constraint, or <i>generation-clause</i> of a generated column references the
+column, an attempt to rename it will generate an error.</note>
+<note type="restriction">The RENAME COLUMN statement
 is not allowed if there are any open cursors that reference the column that
 is being altered.</note>
 <note>If there is an index



Mime
View raw message