Re: [HACKERS] PSQL commands: \quit_if, \quit_unless - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] PSQL commands: \quit_if, \quit_unless
Date
Msg-id CAFj8pRC0LQCpVYDJDXU9V76Vd3rSKGCb0=Ytwv61iYrhPbn1Fg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] PSQL commands: \quit_if, \quit_unless  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers


2016-12-16 21:18 GMT+01:00 Robert Haas <robertmhaas@gmail.com>:
On Fri, Dec 16, 2016 at 12:28 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> why do you need special operator for negation? there is only one use case.
> It can be solved by \if_not

That's exactly the kind of thing I *don't* want to do.  If you
absolutely must have that and you can't wait until we get a full-blown
expression evaluator, then just swap the \if side with the \else side
and call it good.  The whole point here is to avoid introducing weird
hacks for lack of a full expression evaluator that will just become
annoyances once we have one.

I don't need it. Because we don't expect expression there, then "not" or "if_not" is not necessary.

Regards

Pavel
 

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] PSQL commands: \quit_if, \quit_unless
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] pg_dump vs. TRANSFORMs