postgres.git / summary / log / commit / refs

commit    5f286c02423f28c8e4c4d07569417a3d4f40f1a0
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Thu Mar 19 17:02:09 2015 +0000
First released in: 9.5.0

    doc:  ALTER DOMAIN VALIDATE CONSTRAINT can also fail
    
    Document that ALTER DOMAIN VALIDATE CONSTRAINT can also fail for
    composite types.
    
    Report by Ondřej Bouda


 doc/src/sgml/ref/alter_domain.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/ref/alter_domain.sgml b/doc/src/sgml/ref/alter_domain.sgml
index f738b2948b3..ac9a5b3f87d 100644
--- a/doc/src/sgml/ref/alter_domain.sgml
+++ b/doc/src/sgml/ref/alter_domain.sgml
@@ -271,9 +271,9 @@ ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
   <title>Notes</title>
 
   <para>
-   Currently, <command>ALTER DOMAIN ADD CONSTRAINT</> and
-   <command>ALTER DOMAIN SET NOT NULL</> will fail if the validated named
-   domain or
+   Currently, <command>ALTER DOMAIN ADD CONSTRAINT</>, <command>ALTER
+   DOMAIN VALIDATE CONSTRAINT</>, and <command>ALTER DOMAIN SET NOT NULL</>
+   will fail if the validated 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.


[parent: bf740ce9e5d8]