| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Jones | 2008-12-24 23:41:20 | Re: lack of consequence with domains and types |
| Previous Message | Tom Lane | 2008-12-24 17:14:50 | Re: Compiling 8.4devel on OpenSolaris2008.11 with SunStudioExpress |