Re: Nested CASE-WHEN scoping
От | Tom Lane |
---|---|
Тема | Re: Nested CASE-WHEN scoping |
Дата | |
Msg-id | 23055.1306765290@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Nested CASE-WHEN scoping (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
Ответы |
Re: Nested CASE-WHEN scoping
|
Список | pgsql-hackers |
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: > I think we can work around both of those by just saving and restoring > the value of each Param that we set while evaluating an expression, Huh? That's a waste of time and effort. Just make sure that each such spot has its own Param number. That's why I'm telling you to do it in the planner, not the parser --- it is easy to assign globally-unique- across-the-plan numbers at plan time, in fact we do it already. > For debugging purposes, it seems like a good idea to invent a new kind > of Param for these, and keep them separate from PARAM_EXEC params. I'd vote against that too. PARAM_EXEC Params already have more than one purpose. regards, tom lane
В списке pgsql-hackers по дате отправления: