Re: [HACKERS] PSQL commands: \quit_if, \quit_unless

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: [HACKERS] PSQL commands: \quit_if, \quit_unless
Дата
Msg-id CAKFQuwYG7wPrC1tDdL2BchsMucmmp7-XraBpr8kbYcbf_C_4Aw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] PSQL commands: \quit_if, \quit_unless  (Pavel Stehule <pavel.stehule@gmail.com>)
Ответы Re: [HACKERS] PSQL commands: \quit_if, \quit_unless  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers
Дерево обсуждения
On Fri, Dec 16, 2016 at 10:28 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
2016-12-16 18:21 GMT+01:00 David G. Johnston <david.g.johnston@gmail.com>:
On Fri, Dec 16, 2016 at 9:55 AM, Robert Haas <robertmhaas@gmail.com> wrote:

If the expected committed patch set includes #5 then this becomes a matter for reviewer convenience so never mind.  But if its at all possible for #5 to be punted down the road incorporating the eventual "not var" and "not(var)" syntax into #1 as a kind of shim would seem desirable.

why do you need special operator for negation? there is only one use case. It can be solved by \if_not 

​Not following the thread that closely and the section Robert quoted didn't include "\if_not" as a syntax option.  I figured the idea was to limit the number of backslash commands and leave the power in the expression evaluation.

David J.
​

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] Creating a DSA area to provide work space for parallel execution
Следующее
От: Andres Freund
Дата:
Сообщение: Re: [HACKERS] Performance degradation in Bitmapscan (commit75ae538bc3168bf44475240d4e0487ee2f3bb376)