Re: generated constraint name

2025-04-29 Thread Peter Eisentraut
On 24.04.25 17:13, Robert Treat wrote: On Fri, Apr 11, 2025 at 8:45 AM Euler Taveira wrote: On Fri, Apr 11, 2025, at 5:32 AM, Yaroslav Saburov wrote: On the tutorial-agg page in the code example SELECT city FROM weather WHERE temp_lo = max(temp_lo); WRONG you need to add a comment before WRON

Re: generated constraint name

2025-04-24 Thread Robert Treat
On Fri, Apr 11, 2025 at 8:45 AM Euler Taveira wrote: > On Fri, Apr 11, 2025, at 5:32 AM, Yaroslav Saburov wrote: > On the tutorial-agg page in the code example > > SELECT city FROM weather WHERE temp_lo = max(temp_lo); WRONG > > you need to add a comment before WRONG > > If you consider that that

Re: generated constraint name

2025-04-11 Thread Euler Taveira
On Fri, Apr 11, 2025, at 5:32 AM, Yaroslav Saburov wrote: > > Thank you all. > > > > In order not to open a new thread, (small clarification) > Don't be afraid to open a new thread. Indeed, a new topic (even if it is minimal) deserves a new thread. > On the tutorial-agg page in the code exam

Re: generated constraint name

2025-04-11 Thread Yaroslav Saburov
te; or perhaps I did realize that but figured > it was still applicable to versions in the field.) > > I concur with David that we should just drop the para. It's merely > confusing now. If you have a generated constraint name, it won't > require double-quoting unless your table or column name does, and > if they do you are doubtless already quite familiar with how > quoting works. > >regards, tom lane

Re: generated constraint name

2025-04-10 Thread Tom Lane
s still applicable to versions in the field.) I concur with David that we should just drop the para. It's merely confusing now. If you have a generated constraint name, it won't require double-quoting unless your table or column name does, and if they do you are doubtless already quite familiar with how quoting works. regards, tom lane

Re: generated constraint name

2025-04-10 Thread Peter Eisentraut
url: https://www.postgresql.org/docs/current/ddl-alter.html#DDL-ALTER- REMOVING-A-CONSTRAINT <https://www.postgresql.org/docs/current/ddl- alter.html#DDL-ALTER-REMOVING-A-CONSTRAINT> (If you are dealing with a generated constraint name like $2, don't forget

Re: generated constraint name

2025-04-08 Thread Yaroslav Saburov
ged on the website: >> >> Page: https://www.postgresql.org/docs/17/ddl-alter.html >> Description: >> >> url: >> https://www.postgresql.org/docs/current/ddl-alter.html#DDL-ALTER-REMOVING-A-CONSTRAINT >> >> (If you are dealing with a generated constraint na

Re: generated constraint name

2025-04-07 Thread David G. Johnston
gt; DDL-ALTER-REMOVING-A-CONSTRAINT > > (If you are dealing with a generated constraint name like $2, don't forget > that you'll need to double-quote it to make it a valid identifier.) > > If I have a constraint with the name $2, are there other constraints with > names $1, $3

generated constraint name

2025-04-07 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/17/ddl-alter.html Description: url: https://www.postgresql.org/docs/current/ddl-alter.html#DDL-ALTER-REMOVING-A-CONSTRAINT (If you are dealing with a generated constraint name like $2