Re: CREATE DOMAIN create two not null constraints
jian he <jian.universality@gmail.com>
From: jian he <jian.universality@gmail.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2025-06-02T03:15:19Z
Lists: pgsql-hackers
On Mon, Jun 2, 2025 at 12:13 AM Álvaro Herrera <alvherre@kurilemu.de> wrote:
>
> 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),
I don't have a preference.
error out would be fine, since it's a corner case.
Commits
-
Prevent creation of duplicate not-null constraints for domains
- 8af310b33194 18.0 landed
- 647cffd2f321 19 (unreleased) landed
-
Some "feature not supported" errors are better syntax errors, because the
- 33d4c828fde8 7.4.1 cited