From 4a898fbb206f5fb93b4701f6f71d67715e6a1498 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 11 May 2007 20:18:21 +0000
Subject: Fix my oversight in enabling domains-of-domains: ALTER DOMAIN ADD
 CONSTRAINT needs to check the new constraint against columns of derived
 domains too.

Also, make it error out if the domain to be modified is used within any
composite-type columns.  Eventually we should support that case, but it seems
a bit painful, and not suitable for a back-patch.  For the moment just let the
user know we can't do it.

Backpatch to 8.2, which is the only released version that allows nested
domains.  Possibly the other part should be back-patched further.
---
 doc/src/sgml/ref/alter_domain.sgml | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

(limited to 'doc/src')

diff --git a/doc/src/sgml/ref/alter_domain.sgml b/doc/src/sgml/ref/alter_domain.sgml
index 08a26636acd..84dad9d0674 100644
--- a/doc/src/sgml/ref/alter_domain.sgml
+++ b/doc/src/sgml/ref/alter_domain.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/alter_domain.sgml,v 1.20 2006/09/16 00:30:16 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/alter_domain.sgml,v 1.20.2.1 2007/05/11 20:17:31 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -197,6 +197,19 @@ ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
    </para>
   </refsect1>
 
+ <refsect1>
+  <title>Notes</title>
+
+  <para>
+   Currently, <command>ALTER DOMAIN ADD CONSTRAINT</> and
+   <command>ALTER DOMAIN SET NOT NULL</> will fail if the named domain or
+   any derived domain is used within a composite-type column of any
+   table in the database.  They should eventually be improved to be
+   able to verify the new constraint for such nested columns.
+  </para>
+
+ </refsect1>
+
  <refsect1>
   <title>Examples</title>
 
-- 
cgit v1.2.3