| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RfD: more powerful "any" types |
| Date: | 2009-09-08 17:28:48 |
| Message-ID: | 13655.1252430928@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> David E. Wheeler wrote:
>> Why can't anyelement be freed from this constraint?
> Because it would break other uses of it, I think.
Specifically, what are you going to do with something like
make_array(anyelement, anyelement) returns anyarray
There's no principled way to determine what anyarray means if the
arguments are not the same type.
I have no objection to adding some other pseudotype with different
behavior, but breaking anyelement is not the path.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-09-08 17:32:22 | Re: RfD: more powerful "any" types |
| Previous Message | David E. Wheeler | 2009-09-08 17:23:43 | Re: RfD: more powerful "any" types |