Skip to content

Commit d89335e

Browse files
committed
Doc: remove long-obsolete advice about generated constraint names.
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
1 parent f27eb03 commit d89335e

File tree

1 file changed

+0
-3
lines changed

1 file changed

+0
-3
lines changed

doc/src/sgml/ddl.sgml

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1764,9 +1764,6 @@ ALTER TABLE products ALTER COLUMN product_no SET NOT NULL;
17641764
<programlisting>
17651765
ALTER TABLE products DROP CONSTRAINT some_name;
17661766
</programlisting>
1767-
(If you are dealing with a generated constraint name like <literal>$2</literal>,
1768-
don't forget that you'll need to double-quote it to make it a valid
1769-
identifier.)
17701767
</para>
17711768

17721769
<para>

0 commit comments

Comments
 (0)