| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Implicit casts with generic arrays |
| Date: | 2007-06-06 15:23:00 |
| Message-ID: | 28088.1181143380@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> I do have a plan B if people don't want to rename the operators, though.
>> It looks to me like we could eliminate the conflict if we invented a new
>> polymorphic pseudotype called "anynonarray" or some such, which would
>> act like anyelement *except* it would not match an array.
>> ...
>> I was a bit hesitant to propose this since I couldn't immediately think
>> of any other use-case for such a pseudotype. It's not a huge amount of
>> added code (cf. anyenum) but it's definitely a visible wart on the type
>> system. Comments?
> On the contrary, I would think that it fits nicely to "close the loop"
> on the anyarray/anyelement feature set.
OK, I'll go code this up and verify that it behaves like I think it will...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-06-06 15:24:53 | Re: TOAST usage setting |
| Previous Message | Tom Lane | 2007-06-06 15:03:25 | Re: Controlling Load Distributed Checkpoints |