- Notifications
You must be signed in to change notification settings - Fork5
Commit04db9d2
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 thesame name for the same relation. When you create a constraint and specifythe same name explictly, an error is raised. Implicit constraint creationwon't choose an existing name either and up to now you could not rename aconstraint. Renaming works with the patch I sent in a few hours ago but thispatch as well won't allow constraints with identical names on the samerelation.The attached patch thus removes the note in the docs.Joachim Wieland1 parentc03aa1f commit04db9d2
1 file changed
+2
-5
lines changedLines changed: 2 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | | - | |
| 2 | + | |
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
| |||
183 | 183 | | |
184 | 184 | | |
185 | 185 | | |
186 | | - | |
187 | | - | |
188 | | - | |
189 | | - | |
| 186 | + | |
190 | 187 | | |
191 | 188 | | |
192 | 189 | | |
| |||
0 commit comments
Comments
(0)