On Mar 25, 2011, at 9:12 PM, Robert Haas wrote: > > As I've said before, I believe that the root cause of this problem is > that using the same syntax for variables and column names is a bad > idea in the first place. If we used $foo or ?foo or ${foo} or $.foo > or &&foo!!$#? to mean "the parameter called foo", then this would all > be a non-issue.
Yes *please*. Man that would make maintenance of such functions easier. Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers