pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedMissing "CONSTRAINT" keyword in ADD CONSTRAINT form?
3+ messages / 3 participants
[nested] [flat]
* Missing "CONSTRAINT" keyword in ADD CONSTRAINT form?
@ 2023-12-04 20:28 PG Doc comments form <noreply@postgresql.org>
2023-12-04 20:38 ` Re: Missing "CONSTRAINT" keyword in ADD CONSTRAINT form? Tim Needham <tim.needham2@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: PG Doc comments form @ 2023-12-04 20:28 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: tim.needham2@gmail.com
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/sql-alterdomain.html
Description:
(apologies, I managed to send this too soon, just now, somehow)
The example for ALTER DOMAIN shows:
ALTER DOMAIN zipcode ADD CONSTRAINT zipchk CHECK (char_length(VALUE) = 5);
...yet the syntax suggests no CONSTRAINT-keyword (I'm guessing?) should be
used:
ALTER DOMAIN name ADD domain_constraint [ NOT VALID ]
When it should, I think?
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Missing "CONSTRAINT" keyword in ADD CONSTRAINT form?
2023-12-04 20:28 Missing "CONSTRAINT" keyword in ADD CONSTRAINT form? PG Doc comments form <noreply@postgresql.org>
@ 2023-12-04 20:38 ` Tim Needham <tim.needham2@gmail.com>
2023-12-04 20:46 ` Re: Missing "CONSTRAINT" keyword in ADD CONSTRAINT form? David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Tim Needham @ 2023-12-04 20:38 UTC (permalink / raw)
To: tim.needham2@gmail.com; pgsql-docs@lists.postgresql.org
Bah, scratch that, sorry again. It's because "CONSTRAINT" is implied by the
reference to CREATE DOMAIN, isn't it?
Sorry.
On Mon, Dec 4, 2023 at 8:29 PM PG Doc comments form <noreply@postgresql.org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/16/sql-alterdomain.html
> Description:
>
> (apologies, I managed to send this too soon, just now, somehow)
>
> The example for ALTER DOMAIN shows:
>
> ALTER DOMAIN zipcode ADD CONSTRAINT zipchk CHECK (char_length(VALUE) = 5);
>
> ...yet the syntax suggests no CONSTRAINT-keyword (I'm guessing?) should be
> used:
>
> ALTER DOMAIN name ADD domain_constraint [ NOT VALID ]
>
> When it should, I think?
>
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Missing "CONSTRAINT" keyword in ADD CONSTRAINT form?
2023-12-04 20:28 Missing "CONSTRAINT" keyword in ADD CONSTRAINT form? PG Doc comments form <noreply@postgresql.org>
2023-12-04 20:38 ` Re: Missing "CONSTRAINT" keyword in ADD CONSTRAINT form? Tim Needham <tim.needham2@gmail.com>
@ 2023-12-04 20:46 ` David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 0 replies; 3+ messages in thread
From: David G. Johnston @ 2023-12-04 20:46 UTC (permalink / raw)
To: Tim Needham <tim.needham2@gmail.com>; +Cc: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
On Monday, December 4, 2023, Tim Needham <tim.needham2@gmail.com> wrote:
> Bah, scratch that, sorry again. It's because "CONSTRAINT" is implied by
> the reference to CREATE DOMAIN, isn't it?
>
Yes, we require the reader to go to the create domain page to read the
“domain_constraint” portion of the syntax.
David J.
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2023-12-04 20:46 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-12-04 20:28 Missing "CONSTRAINT" keyword in ADD CONSTRAINT form? PG Doc comments form <noreply@postgresql.org>
2023-12-04 20:38 ` Tim Needham <tim.needham2@gmail.com>
2023-12-04 20:46 ` David G. Johnston <david.g.johnston@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox