Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit03faf38

Browse files
committed
Doc: remove long-obsolete advice about generated constraint names.
It's been twenty years since we generated constraint names thatlook like "$N". So this advice about double-quoting such namesis 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.orgBackpatch-through: 13
1 parentcadaf0a commit03faf38

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
@@ -1681,9 +1681,6 @@ ALTER TABLE products ALTER COLUMN product_no SET NOT NULL;
16811681
<programlisting>
16821682
ALTER TABLE products DROP CONSTRAINT some_name;
16831683
</programlisting>
1684-
(If you are dealing with a generated constraint name like <literal>$2</literal>,
1685-
don't forget that you'll need to double-quote it to make it a valid
1686-
identifier.)
16871684
</para>
16881685

16891686
<para>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp