| From: | "Matt Miller" <pgsql(at)mattmillersf(dot)fastmail(dot)fm> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: "anyelement2" pseudotype |
| Date: | 2007-02-14 16:52:06 |
| Message-ID: | 1171471926.27919.1174623763@webmail.messagingengine.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > adding an "anyelement2" pseudotype ... The context was a
> > compatibility SQL function to support Oracle's DECODE function.
>
> 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?
No. Even this case, for me, is more an expedient than a necessity. I
could just rewrite my Oracle code to use CASE, but I've a lot of code to
convert, and the transformation is a bit error prone. I'm also looking
at a scripted code edit to rewrite the Oracle stuff, and comparing this
to the cost a PG compatibility function.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-14 17:03:57 | Re: Plan for compressed varlena headers |
| Previous Message | Jim C. Nasby | 2007-02-14 16:51:21 | Re: NULL and plpgsql rows |