Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 24a1faf

Browse files
committed
Clearify CHECK handling of unknown test values.
Karl O. Pinc
1 parent 4da3685 commit 24a1faf

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

doc/src/sgml/ref/create_table.sgml

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.80 2004/03/22 16:18:50 tgl Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/create_table.sgml,v 1.81 2004/05/19 23:10:43 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -383,10 +383,13 @@ and <replaceable class="PARAMETER">table_constraint</replaceable> is:
383383
<para>
384384
The <literal>CHECK</> clause specifies an expression producing a
385385
Boolean result which new or updated rows must satisfy for an
386-
insert or update operation to succeed. A check constraint
387-
specified as a column constraint should reference that column's
388-
value only, while an expression appearing in a table constraint
389-
may reference multiple columns.
386+
insert or update operation to succeed. Expressions evaluating
387+
to TRUE or UNKNOWN succeed. Should any row of an insert or
388+
update operation produce a FALSE result an error exception is
389+
raised and the insert or update does not alter the database. A
390+
check constraint specified as a column constraint should
391+
reference that column's value only, while an expression
392+
appearing in a table constraint may reference multiple columns.
390393
</para>
391394

392395
<para>

0 commit comments

Comments
 (0)