Re: Implementing standard SQL's DOMAIN constraint [RESOLVED]

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Implementing standard SQL's DOMAIN constraint [RESOLVED]
Date: 2019-01-02 18:13:34
Message-ID: 284b6b1d-3a8f-f0a6-8446-eaf48174a565@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 1/2/19 12:05 PM, Rich Shepard wrote:
> On Wed, 2 Jan 2019, David G. Johnston wrote:
>
>> You add the create domain command once before any objects that make use of
>> it.
>
> David,
>
>   This is the answer I sought: postgres supports the create domain command.
> I did not see this in your first response.

Note that a CHECK constraint with 50 items is a *Very Bad Idea*, since
changing such a constraint is very painful.  Use a FK constraint instead.

--
Angular momentum makes the world go 'round.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2019-01-02 18:19:25 Re: Query planner / Analyse statistics bad estimate rows=1 with maximum statistics 10000 on PostgreSQL 10.2
Previous Message Rich Shepard 2019-01-02 18:05:58 Re: Implementing standard SQL's DOMAIN constraint [RESOLVED]