Closed cwells closed 14 years ago
I should also point out that the following seemingly equivalent config works:
location /x {
set $data $arg_data;
set_quote_sql_str for=pg $data;
}
location /y {
set $data $arg_data;
set_quote_sql_str for=pg $data;
}
Again, this is done by design to avoid "stupid accidents" that happen when same variable is re-used in number of locations.
Hey Cliff, I've just committed major rewrite of postgres_escape
directive which adds ability to re-use variable names... It solves your original issue, so I'm closing this.
great, thanks!
A config like the following config fails:
result is error such as:
Replacing "postgres_escape" with "set" does not result in similar error.