8000 doc: ALTER DOMAIN VALIDATE CONSTRAINT can also fail · sarvex/postgres@5f286c0 · GitHub
[go: up one dir, main page]
Skip to content

Commit 5f286c0

Browse files
bmomjianbmomjian
committed
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
1 parent bf740ce commit 5f286c0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎doc/src/sgml/ref/alter_domain.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -271,9 +271,9 @@ ALTER DOMAIN <replaceable class="PARAMETER">name</replaceable>
271271
<title>Notes</title>
272272

273273
<para>
274-
Currently, <command>ALTER DOMAIN ADD CONSTRAINT</> and
275-
<command>ALTER DOMAIN SET NOT NULL</> will fail if the validated named
276-
domain or
274+
Currently, <command>ALTER DOMAIN ADD CONSTRAINT</>, <command>ALTER
275+
DOMAIN VALIDATE CONSTRAINT</>, and <command>ALTER DOMAIN SET NOT NULL</>
276+
will fail if the validated named domain or
277277
any derived domain is used within a composite-type column of any
278278
table in the database. They should eventually be improved to be
279279
able to verify the new constraint for such nested columns.

0 commit comments

Comments
 (0)
0