Re: [HACKERS] Explicitly specifying use of IN/OUT variable in PL/pgSQL functions

2012-03-13 Thread Tom Lane
Joel Jacobson writes: > In situations when it's natural and makes sense to mix IN/OUT > variables and columns names, it would be nice to being able to > explicitly specifying you are referring to the IN or OUT variable with > a specific name. Can't you qualify them with the function name?

Re: [HACKERS] Explicitly specifying use of IN/OUT variable in PL/pgSQL functions

2012-03-13 Thread Pavel Stehule
Hello you can use function name as qualifier create or replace function fx(paramname type, ...) returns ... begin SELECT INTO fx.paramname, ... Regards Pavel Stehule 2012/3/13 Joel Jacobson : > The introduction of custom_variable_classes and #variable_conflict in > 9.0 partly solves the prob

[HACKERS] Explicitly specifying use of IN/OUT variable in PL/pgSQL functions

2012-03-13 Thread Joel Jacobson
The introduction of custom_variable_classes and #variable_conflict in 9.0 partly solves the problem with mixing IN/OUT variables with column names. In 8.4 and before, it defaulted to the IN/OUT variable, if it shared the name of a column. In 9.0 the behaviour was changed to raise an error if a vari