1- <!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.68 2006/11/21 03:44:55 momjian Exp $ -->
1+ <!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.69 2006/11/28 01:09:01 tgl Exp $ -->
22
33<chapter id="ddl">
44 <title>Data Definition</title>
@@ -2055,10 +2055,9 @@ VALUES ('New York', NULL, NULL, 'NY');
20552055 </para>
20562056
20572057 <para>
2058- Check constraints can be defined on tables within an inheritance
2059- hierarchy. All check constraints on a parent table are
2060- automatically inherited by all of its children. Other types of
2061- constraints are not inherited, however.
2058+ All check constraints and not-null constraints on a parent table are
2059+ automatically inherited by its children. Other types of constraints
2060+ (unique, primary key, and foreign key constraints) are not inherited.
20622061 </para>
20632062
20642063 <para>
@@ -2070,7 +2069,8 @@ VALUES ('New York', NULL, NULL, 'NY');
20702069 so that there is only one such column in the child table. To be merged,
20712070 columns must have the same data types, else an error is raised. The
20722071 merged column will have copies of all the check constraints coming from
2073- any one of the column definitions it came from.
2072+ any one of the column definitions it came from, and will be marked not-null
2073+ if any of them are.
20742074 </para>
20752075
20762076 <para>