On 2025-Jun-01, jian he wrote:
> hi.
>
> CREATE DOMAIN int_domain1 AS INT CONSTRAINT nn1 NOT NULL CONSTRAINT
> nn2 NOT NULL;
>
> will install two not-null pg_constraint entries.
> we should have only one?
Hmm, I think it would be more consistent to reject the case of duplicate
constraints, instead of silently ignoring it. So you'd do it in the
loop that checks for constraints before creating anything, like
diff --git a/src/backend/commands/typecmds.c b/src/backend/commands/typecmds.c
index 45ae7472ab5..b5daa61260b 100644
--- a/src/backend/commands/typecmds.c
+++ b/src/backend/commands/typecmds.c
@@ -944,6 +944,12 @@ DefineDomain(ParseState *pstate, CreateDomainStmt *stmt)
errcode(ERRCODE_SYNTAX_ERROR),
errmsg("conflicting
NULL/NOT NULL constraints"),
parser_errposition(pstate, constr->location));
+
+ if (nullDefined)
+ ereport(ERROR,
+
errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
+ errmsg("redundant NOT
NULL constraint definition"));
+
if (constr->is_no_inherit)
ereport(ERROR,
errcode(ERRCODE_INVALID_OBJECT_DEFINITION),
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Porque Kim no hacía nada, pero, eso sí,
con extraordinario éxito" ("Kim", Kipling)
