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

From Erik Jones
Subject Re: lack of consequence with domains and types
Date
Msg-id E83E368B-6C93-4494-9653-AB8AD329443B@engineyard.com
Whole thread Raw
In response to Re: lack of consequence with domains and types  ("Grzegorz Jaśkiewicz" <gryzman@gmail.com>)
Responses Re: lack of consequence with domains and types  ("Grzegorz Jaśkiewicz" <gryzman@gmail.com>)
List pgsql-general
On Dec 22, 2008, at 1:08 PM, Grzegorz Jaśkiewicz wrote:

> On Mon, Dec 22, 2008 at 6:10 PM, Erik Jones <ejones@engineyard.com>
> wrote:
>> As mentioned above, by "fixing" the behavior to be what you're
>> expecting
>> you'd be breaking the defined behavior of ALTER TABLE.
>
> I don't understand. The domain's have default values, how will it
> break alter table ? Please explain.

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.

Erik Jones, Database Administrator
Engine Yard
Support, Scalability, Reliability
866.518.9273 x 260
Location: US/Pacific
IRC: mage2k






pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: need some help with pl-pgsql
Next
From: Tom Lane
Date:
Subject: Re: Compiling 8.4devel on OpenSolaris2008.11 with SunStudioExpress