Tom Lane-2 wrote
>
>> -- A stored procedure which can accept two argument, which can be a
>> single
>> integer field, or an array of integers.
>
> Those two cases seem unlikely to be supportable by the same
> implementation, so it seems more likely that what you'd be doing is just
> overloading the function name with two instances, my_fn(int) and
> my_fn(int[]).
Isn't this scenario why VARIDIC was implemented:
CREATE FUNCTION my_fn( VARIADIC in_ordered_actual varchar[] ) ....
The single value input is simply a special case of an array of size 1.
Depending on whether you allow an empty array you might want to:
CREATE FUNCTION my_fn(required_first varchar, VARIADIC optional_others
varchar[] DEFAULT '{}'::varchar[]) ...
Then join the two values together and move on to processing.
You would still need separate functions for numbers versus strings.
David J.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Semi-Pseudo-Data-Types-Procedure-Arguments-tp5761158p5761173.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
