Alvaro Herrera writes:
> BTW is there a reason the error messages say "plpgsql functions cannot
> ..." instead of "PL/pgSQL functions cannot ..."?
Somewhere along the line there was the idea that the messages ought to
match the "real" name of the PL language, which is plpgsql. The other
name is
BTW is there a reason the error messages say "plpgsql functions cannot
..." instead of "PL/pgSQL functions cannot ..."?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via pgsql-general m
Decibel! writes:
> Is there a reason we disallow using "any" with SQL functions?
Yes. Try "anyelement" instead.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailp
Is there a reason we disallow using "any" with SQL functions?
deci...@phonebook.local=# create function textcoalesce("any") returns
void language sql as $$SELECT coalesce( $1::text, '' )$$;
ERROR: SQL functions cannot have arguments of type "any"
STATEMENT: create function textcoalesce("any"
