Minor improvements for CHECK NO INHERIT documentation.
Fix typo spotted by Thom Brown, and improve wording in another area where Thom spotted a typo.
This commit is contained in:
parent
48658a1b81
commit
9d435d57e1
@ -906,9 +906,8 @@ ALTER TABLE [ IF EXISTS ] <replaceable class="PARAMETER">name</replaceable>
|
||||
The <literal>TRIGGER</>, <literal>CLUSTER</>, <literal>OWNER</>,
|
||||
and <literal>TABLESPACE</> actions never recurse to descendant tables;
|
||||
that is, they always act as though <literal>ONLY</> were specified.
|
||||
Adding a constraint can recurse only for <literal>CHECK</> constraints,
|
||||
and is required to do so for such constraints, except those that are
|
||||
explicitely marked <literal>NO INHERIT</>.
|
||||
Adding a constraint recurses only for <literal>CHECK</> constraints
|
||||
that are not marked <literal>NO INHERIT</>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
|
@ -438,7 +438,7 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI
|
||||
|
||||
<para>
|
||||
A constraint marked with <literal>NO INHERIT</> will not propagate to
|
||||
children tables.
|
||||
child tables.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
Loading…
Reference in New Issue
Block a user