Re: lack of consequence with domains and types - Mailing list pgsql-general

From Grzegorz Jaśkiewicz
Subject Re: lack of consequence with domains and types
Date
Msg-id 2f4958ff0812241204j104223f5k8eec731c7662d8c4@mail.gmail.com
Whole thread Raw
In response to Re: lack of consequence with domains and types  (Erik Jones <ejones@engineyard.com>)
Responses Re: lack of consequence with domains and types  (Erik Jones <ejones@engineyard.com>)
List pgsql-general
On Wed, Dec 24, 2008 at 6:12 PM, Erik Jones <ejones@engineyard.com> wrote:
> Yes, and columns have default values, too, which are not tied to their
> datatype's default value (if it even has one).  ALTER TABLE initializes rows
> to have the new *column's* default.  A column of some domain type could
> easily have some default other than the domain's default and, in fact, if
> you don't specify a default for the column then it's default is NULL.

the whole thing about domains, is that you specify type and default,
and even check constraint. And I did specify default - hence I would
expect it to be set to that value!!



--
GJ

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Compiling 8.4devel on OpenSolaris2008.11 with SunStudioExpress
Next
From: Erik Jones
Date:
Subject: Re: lack of consequence with domains and types