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

Commit d800b03

Browse files
committed
Document that NOT NULL domain constraints are not always honored.
1 parent 23e9fe0 commit d800b03

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

doc/src/sgml/ref/create_domain.sgml

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.34 2010/04/03 07:22:58 petere Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.35 2010/05/29 19:06:16 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -121,7 +121,12 @@ CREATE DOMAIN <replaceable class="parameter">name</replaceable> [ AS ] <replacea
121121
<term><literal>NOT NULL</></term>
122122
<listitem>
123123
<para>
124-
Values of this domain are not allowed to be null.
124+
Values of this domain are normally prevented from being null.
125+
However, it is still possible for a domain with this constraint
126+
to take a null value if it is assigned a matching domain type
127+
that has become null, e.g. via a LEFT OUTER JOIN, or
128+
<command>INSERT INTO tab (domcol) VALUES ((SELECT domcol FROM
129+
tab WHERE false))</command>.
125130
</para>
126131
</listitem>
127132
</varlistentry>

0 commit comments

Comments
 (0)