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-03-08 05:05:11 |
Message-ID: | 5693.1015563911@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:
> find how to use it. Just that I noticed a TODO item stating that
> everything should have one. I guess I don't understand -- among other
> things -- why DomainStmt needs to be copied?
If it's not copiable then it will fail when used in plpgsql, among
probably other problems. In general there should be no parse
node types that don't have copyObject() and equal() support; and also
outfuncs.c support, for debugging dumps if nothing else. We've been
relatively lax on insisting on readfuncs.c support --- that really only
matters for constructs that can appear in rules.
> MergeDomainAttributes pushes the domains configuration onto a table
> field during table creation where the field type is a domain.
Ah. I had it backwards: thought it was pulling constraints into the
domain definition from elsewhere.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-03-08 05:15:02 | Re: Index USING in pg_dump |
Previous Message | Tom Lane | 2002-03-08 04:53:03 | Re: Small fix for _valueCopy() |