| From: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | HACKERS <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Multiple anyelement types |
| Date: | 2008-08-11 09:31:40 |
| Message-ID: | 20080811181203.9A32.52131E4D@oss.ntt.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I'm working on improvements of orafce.
http://pgfoundry.org/projects/orafce
I found postgres supports only one type of anyelement at one time
when I added nvl2() and decode(). I'd like to use multiple types of
anyelement something like:
template < typename Expr, typename Ret >
CREATE FUNCTION nvl(Expr, Ret, Ret) RETURNS Ret
template < typename Expr, typename Ret >
CREATE FUNCTION decode(Expr, Expr, Ret, ..., Ret) RETURNS Ret
I don't mean to propose the above C++-like syntax, but such feature
is important to develop a generic porting tool. Two independent
anyelements are enough for me, but three or more might be better
for general use.
What syntax is suitable for postgres? Comments welcome.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-08-11 10:58:08 | Re: Proposal: PageLayout footprint |
| Previous Message | Gregory Stark | 2008-08-11 09:24:31 | Re: Question regarding the database page layout. |