| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Matt Miller" <pgsql(at)mattmillersf(dot)fastmail(dot)fm> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: "anyelement2" pseudotype |
| Date: | 2007-02-14 07:27:32 |
| Message-ID: | 18884.1171438052@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Matt Miller" <pgsql(at)mattmillersf(dot)fastmail(dot)fm> writes:
> A few months ago at
> http://archives.postgresql.org/pgsql-general/2006-11/msg01770.php the
> notion of adding an "anyelement2" pseudotype was discussed. The context
> was a compatibility SQL function to support Oracle's DECODE function.
> Assuming this new pseudotype has not been added yet, I'm ready to look
> into doing this myself, and I'd like a bit of shove in the right direction.
The reason it's not in there already is we didn't seem to have quite
enough use-case to justify it. Do you have more?
As for actually adding it, grep for all references to ANYELEMENT and add
code accordingly; shouldn't be that hard. Note you'd need to add an
anyarray2 at the same time for things to keep working sanely.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2007-02-14 09:13:14 | Re: HOT for PostgreSQL 8.3 |
| Previous Message | Peter Eisentraut | 2007-02-14 07:15:14 | [ANNOUNCE] Advisory on possibly insecure security definer functions |