On Tue, Nov 27, 2012 at 10:52 AM, Pavel Stehule <pavel.steh...@gmail.com> wrote: > it is a basic problem - PostgreSQL has unique possibilities - > polymorphic parameters and almost all databases doesn't support > overloading
Speaking of polymorphism, why not just implement lpad()'s first argument as 'anyelement'? ISTM this comes up in mostly in porting code from other database that is utilizing standard sql functions. This should be appropriate when the function's basic functionality and argument signature is not dependent on input type (constrast: to_timestamp) and there is a good portability case to be made. Essentially, this applies to a handful of string processing routines AFAICT. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
