"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> select foo(777, three=> '{1,2,3,4,5});
> it's more safe and more readable.
... and it breaks an operator that's already in use.
> I did some test, and I thing so it is implementable. I had to solve
> problem with hstore module. There is defined operator => too, what is
> bad. But we can implemented in transformation and it should by
> disabled via GUC, so it's solveable.
What's wrong with the "expr AS parameter_name" syntax that we've
discussed before? (And no, having a GUC that changes the meaning
of "=>" isn't an acceptable workaround.)
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
