Re: Implementing standard SQL's DOMAIN constraint

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Implementing standard SQL's DOMAIN constraint
Date: 2019-01-02 17:58:41
Message-ID: alpine.LNX.2.20.1901020956260.20959@salmo.appl-ecosys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, 2 Jan 2019, David G. Johnston wrote:

>> I'm not following you. I have two tables each with a column,
>> state_code char(2) NOT NULL.

> That is a char(2) column for which ‘??’ is a valid value. The fact that it
> is named state_code is immaterial; the domain that you created doesn’t get
> used. There is no magic linking just by virtue of using the same name.
>
> Change char(2) to state_code if you wish to apply the domain on the column.

David,

I think I'm now on your page. In the schema I change the column data type
to state_code, then I add the SQL code creating the domain at the top of the
.sql file. Yes?

Thanks,

Rich

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2019-01-02 18:02:24 Re: Implementing standard SQL's DOMAIN constraint
Previous Message David G. Johnston 2019-01-02 17:52:43 Re: Implementing standard SQL's DOMAIN constraint