aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNeil Conway <neilc@samurai.com>2006-06-28 22:01:52 +0000
committerNeil Conway <neilc@samurai.com>2006-06-28 22:01:52 +0000
commit6e9c974e437b2e455a6362cfbfef3fc48e66280c (patch)
tree1dcca48c40a9f4376577273735a531ef8db07fc6
parent06bd3dba803eab1d2113f7ae9875b21482c78eba (diff)
downloadpostgresql-6e9c974e437b2e455a6362cfbfef3fc48e66280c.tar.gz
postgresql-6e9c974e437b2e455a6362cfbfef3fc48e66280c.zip
Editorialization for the additions to the CREATE TABLE reference page
made as part of the recent INCLUDING CONSTRAINTS patch. The text could stand further improvement, but this is at least a step in the right direction.
-rw-r--r--doc/src/sgml/ref/create_table.sgml20
1 files changed, 10 insertions, 10 deletions
diff --git a/doc/src/sgml/ref/create_table.sgml b/doc/src/sgml/ref/create_table.sgml
index 916f0c8b568..0276dc7ad23 100644
--- a/doc/src/sgml/ref/create_table.sgml
+++ b/doc/src/sgml/ref/create_table.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.101 2006/06/27 03:43:19 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.102 2006/06/28 22:01:52 neilc Exp $
PostgreSQL documentation
-->
@@ -249,19 +249,19 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
<para>
Default expressions for the copied column definitions will only be
copied if <literal>INCLUDING DEFAULTS</literal> is specified. The
- default behavior is to exclude default expressions, resulting in
- all columns of the new table having null defaults.
+ default behavior is to exclude default expressions, resulting in the
+ copied columns in the new table having null defaults.
</para>
<para>
- Likewise constraints for the copied column definitions will only be
- copied if <literal>INCLUDING CONSTRAINTS</literal> is specified. Note
- that currently even when <literal>INCLUDING CONSTRAINTS</literal> is specified
- only CHECK constraints are copied. Also, no distinction is made between
- column constraints and table constraints -- when constraints are
- requested all check constraints are copied.
+ Not-null constraints are always copied to the new table.
+ <literal>CHECK</literal> constraints will only be copied if
+ <literal>INCLUDING CONSTRAINTS</literal> is specified; other types of
+ constraints will never be copied. Also, no distinction is made between
+ column constraints and table constraints &mdash; when constraints are
+ requested, all check constraints are copied.
</para>
<para>
- Note also that unlike <literal>INHERITS<literal> copied columns and
+ Note also that unlike <literal>INHERITS</literal>, copied columns and
constraints are not merged with similarly named columns and constraints.
If the same name is specified explicitly or in another
<literal>LIKE</literal> clause an error is signalled.