Re: Drop column constraint [FIXED]
От | Adrian Klaver |
---|---|
Тема | Re: Drop column constraint [FIXED] |
Дата | |
Msg-id | 321fb1d3-7780-ebda-7bfe-06720f5d87a8@aklaver.com обсуждение исходный текст |
Ответ на | Re: Drop column constraint [FIXED] (Rich Shepard <rshepard@appl-ecosys.com>) |
Ответы |
Re: Drop column constraint [FIXED]
|
Список | pgsql-general |
On 10/30/20 8:54 AM, Rich Shepard wrote: > On Fri, 30 Oct 2020, Adrian Klaver wrote: > >> It should be: >> alter table locations drop constraint 'constraint_name'; > > Adrian, > > Yes, I forgot to quote the constraint_name, And, I used the DDL name > 'unique' rather than the internal name "locations_loc_nbr_key". Using the Actually unique is not the name, it is the constraint type. You can create your own name when creating the constraint or Postgres will create one for you. > latter, and adding 'cascade' (because the dependent table is empty) did the > trick. > > Thank you, > > Rich > > > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: