Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 04db9d2

Browse files
committed
there's a paragraph in the ALTER TABLE reference page that reads:
DROP CONSTRAINT This form drops constraints on a table. Currently, constraints on tables are not required to have unique names, so there may be more than one constraint matching the specified name. All matching constraints will be dropped. To my knowledge, it is no longer possible to create constraints with the same name for the same relation. When you create a constraint and specify the same name explictly, an error is raised. Implicit constraint creation won't choose an existing name either and up to now you could not rename a constraint. Renaming works with the patch I sent in a few hours ago but this patch as well won't allow constraints with identical names on the same relation. The attached patch thus removes the note in the docs. Joachim Wieland
1 parent c03aa1f commit 04db9d2

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

doc/src/sgml/ref/alter_table.sgml

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.81 2005/08/24 17:24:19 tgl Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/alter_table.sgml,v 1.82 2005/12/08 21:35:36 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -183,10 +183,7 @@ where <replaceable class="PARAMETER">action</replaceable> is one of:
183183
<term><literal>DROP CONSTRAINT</literal></term>
184184
<listitem>
185185
<para>
186-
This form drops constraints on a table.
187-
Currently, constraints on tables are not required to have unique
188-
names, so there may be more than one constraint matching the specified
189-
name. All matching constraints will be dropped.
186+
This form drops the specified constraint on a table.
190187
</para>
191188
</listitem>
192189
</varlistentry>

0 commit comments

Comments
 (0)