| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Rod Taylor" <rbt(at)zort(dot)ca> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Basic DOMAIN Support |
| Date: | 2002-02-25 02:29:09 |
| Message-ID: | 14370.1014604149@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
"Rod Taylor" <rbt(at)zort(dot)ca> writes:
> Did that originally with a function called MergeDomainAttributes()
> (since removed). The goal was to allow the user to change table
> attributes without overriding the domain. The constraints are
> 'merged' on execution for every other constraint type (default is
> wacky though), so don't see why NOT NULL should be special.
It appeared to me that the intention was to merge at table creation
time, not at execution. I would certainly recommend doing it that
way for simplicity and performance reasons. (This does put ALTER DOMAIN
out of reach, but I feel no pain at not supporting that.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-02-25 02:52:04 | Re: [HACKERS] Updated TODO item |
| Previous Message | Rod Taylor | 2002-02-25 02:24:49 | Re: Basic DOMAIN Support |