Document that NOT NULL domain constraints are not always honored.

diff --git a/doc/src/sgml/ref/create_domain.sgml b/doc/src/sgml/ref/create_domain.sgml
index 637326b58bbbe74bb45ec110377e7a3bd20f6211..eb3bb3d98232a7e85f4a2d6eb10974fdcb2e757e 100644 (file)
--- a/doc/src/sgml/ref/create_domain.sgml
+++ b/doc/src/sgml/ref/create_domain.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.34 2010/04/03 07:22:58 petere Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/create_domain.sgml,v 1.35 2010/05/29 19:06:16 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -121,7 +121,12 @@ CREATE DOMAIN <replaceable class="parameter">name</replaceable> [ AS ] <replacea
       <term><literal>NOT NULL</></term>
       <listitem>
        <para>
-        Values of this domain are not allowed to be null.
+        Values of this domain are normally prevented from being null.
+        However, it is still possible for a domain with this constraint
+        to take a null value if it is assigned a matching domain type
+        that has become null, e.g. via a LEFT OUTER JOIN, or
+        <command>INSERT INTO tab (domcol) VALUES ((SELECT domcol FROM
+        tab WHERE false))</command>.
        </para>
       </listitem>
      </varlistentry>