Skip site navigation (1) Skip section navigation (2)

Re: lack of consequence with domains and types

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: "Erik Jones" <ejones(at)engineyard(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: lack of consequence with domains and types
Date: 2008-12-24 20:04:34
Message-ID: 2f4958ff0812241204j104223f5k8eec731c7662d8c4@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
On Wed, Dec 24, 2008 at 6:12 PM, Erik Jones <ejones(at)engineyard(dot)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

In response to

Responses

pgsql-general by date

Next:From: Erik JonesDate: 2008-12-24 23:41:20
Subject: Re: lack of consequence with domains and types
Previous:From: Tom LaneDate: 2008-12-24 17:14:50
Subject: Re: Compiling 8.4devel on OpenSolaris2008.11 with SunStudioExpress

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group