Re: Default column value

From: Rich Shepard <rshepard(at)appl-ecosys(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Default column value
Date: 2016-12-30 16:19:01
Message-ID: alpine.LNX.2.11.1612300815330.11546@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, 30 Dec 2016, Adrian Klaver wrote:

> DEFAULT is what is the column is set to if the user does not specify a
> value. As shown above a user can supply a NULL value. To guard against
> that the NOT NULL constraint is required.

One more case I'd appreciate being clarified: when the column's value has
a check constraint with acceptable values in a list. For example,

param_units VARCHAR(8) DEFAULT 'mg/L'
CONSTRAINT param_units
CHECK (param_units IN ('ppm', 'mg/L', 'ug/L', 'umho/cm', 'percent', 'cfm', 'gpm')),

Seems to me that if values are constrained by a list a NULL cannot be
entered by the user. Is this correct?

Rich

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2016-12-30 16:29:07 Re: Default column value
Previous Message Melvin Davidson 2016-12-30 16:06:41 Re: LYDB: Feasible to use PG roles instead of application-level security?