Re: Alter table column constraint - Mailing list pgsql-general

From Rich Shepard
Subject Re: Alter table column constraint
Date
Msg-id alpine.LNX.2.20.1812171217570.741@salmo.appl-ecosys.com
Whole thread Raw
In response to Re: Alter table column constraint  (Melvin Davidson <melvin6925@gmail.com>)
Responses Re: Alter table column constraint  (Ron <ronljohnsonjr@gmail.com>)
Re: Alter table column constraint  ("David G. Johnston" <david.g.johnston@gmail.com>)
Re: Alter table column constraint  (Melvin Davidson <melvin6925@gmail.com>)
Re: Alter table column constraint  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
On Mon, 17 Dec 2018, Melvin Davidson wrote:

> Yes, you must drop then add the revised constraint. However, from your
> statement above, it sounds to me as if you would be better off using A
> FOREIGN kEY CONSTRAINT. It makes things a lot simpler.

Melvin,

   I don't follow. Here's the DDL for that column:

industry varchar(24) NOT NULL
     CONSTRAINT invalid_industry
     CHECK (industry in ('Agriculture', 'Business, other', 'Chemicals',
     'Energy', 'Law', 'Manufacturing', 'Mining', 'Municipalities',
     'Ports/Marine Services', 'Transportation')),

and I want to remove Municipalities for the more general Government.

Regards,

Rich


pgsql-general by date:

Previous
From: Melvin Davidson
Date:
Subject: Re: Alter table column constraint
Next
From: "Kumar, Virendra"
Date:
Subject: RE: NL Join vs Merge Join - 5 hours vs 2 seconds