| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | ramsiddu007 <ramsiddu007(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Function Overloading |
| Date: | 2018-05-24 13:52:31 |
| Message-ID: | 23422.1527169951@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
ramsiddu007 <ramsiddu007(at)gmail(dot)com> writes:
> I hope you are all doing good. Actually I got one problem. I
> have 2 functions like below. Those are having 11 and 14 parameters with
> commonly last parameter is variadic array type.
> func_get_item_list_phy_param(smallint, numeric, numeric, character varying,
> character varying, character varying, numeric, character varying, integer,
> integer, character varying[]);
> func_get_item_list_phy_param(smallint, numeric, numeric, character varying,
> character varying, character varying, numeric, character varying, integer,
> integer, character varying, character varying, character varying, character
> varying[]);
Don't do that. There's no way for the system to figure out which one it
should call if you have >= 14 actual parameters, because they both match
the call equally well.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2018-05-24 14:33:11 | Locks on unlogged tables are locked?! |
| Previous Message | Kyotaro HORIGUCHI | 2018-05-24 13:00:57 | Re: A Japanese-unfriendy error message contruction |