Re: [HACKERS] Undefined psql variables
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] Undefined psql variables |
Дата | |
Msg-id | 11154.1485193991@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | [HACKERS] Undefined psql variables (Corey Huinker <corey.huinker@gmail.com>) |
Ответы |
Re: [HACKERS] Undefined psql variables
Re: [HACKERS] Undefined psql variables Re: Undefined psql variables |
Список | pgsql-hackers |
Corey Huinker <corey.huinker@gmail.com> writes: > I was giving some thought to how psql handles undefined variables. > I would like an option where either psql can provide an alternate value > when an undefined variable is referenced, or a way to detect that a > specific variable is undefined and replace it with a defined variable. This seems pretty bizarre. What's the use case? Why would it not be better to build the behavior out of other spare parts, along the lines of COALESCE or perhaps \if not defined(x) \set x y \fi Obviously the \if stuff is things we don't have yet either, but it seems less likely to have surprising side-effects. regards, tom lane
В списке pgsql-hackers по дате отправления: