| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tom Dunstan <pgsql(at)tomd(dot)cc>, Matt Miller <pgsql(at)mattmillersf(dot)fastmail(dot)fm>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: "anyelement2" pseudotype |
| Date: | 2007-02-15 19:56:16 |
| Message-ID: | 45D4BAE0.4040806@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Come to think of it, we really do need some refactoring in
> parse_coerce.c.
[snip]
> I'm not very sure what a good refactoring would look like,
> but I am sure that I don't want all their call sites having to
> individually account for ANYfoo types. Any thoughts?
>
>
I was just thinking earlier that we need some sort of ANYany(oid) test.
I guess a very simple minded approach would just macro expand it, to
something like what's there now, or if we were more adventurous we could
rearrange things so that a bitmask test would work.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2007-02-15 20:10:56 | Re: patch adding new regexp functions |
| Previous Message | Tom Lane | 2007-02-15 19:46:44 | Re: "anyelement2" pseudotype |