database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-25 21:42:33 +03:00
Code

Doc: remove long-obsolete advice about generated constraint names.

Browse Source 
It's been twenty years since we generated constraint names that
look like "$N".  So this advice about double-quoting such names
is well past its sell-by date, and now it merely seems confusing.

Reported-by: Yaroslav Saburov <y.saburov@gmail.com>
Author: "David G. Johnston" <david.g.johnston@gmail.com>
Discussion: https://postgr.es/m/174393459040.678.17810152410419444783@wrigleys.postgresql.org
Backpatch-through: 13
This commit is contained in:
Tom Lane 2025-04-10 14:49:10 -04:00
parent 0434033e8b
commit 95e83859b9
1 changed files with 0 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/src/sgml/ddl.sgml
View File

@ -1470,9 +1470,6 @@ ALTER TABLE products ALTER COLUMN product_no SET NOT NULL;
<programlisting> <programlisting>
ALTER TABLE products DROP CONSTRAINT some_name; ALTER TABLE products DROP CONSTRAINT some_name;
</programlisting> </programlisting>
(If you are dealing with a generated constraint name like <literal>$2</literal>,
don't forget that you'll need to double-quote it to make it a valid
identifier.)
</para> </para>
<para> <para>