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

From Pavel Stehule
Subject Re: PSQL commands: \quit_if, \quit_unless
Date
Msg-id CAFj8pRAkiBkDVmao+TEU=Y28dv1C12xOUVF20m5VGD-0oEwKDg@mail.gmail.com
Whole thread Raw
In response to Re: PSQL commands: \quit_if, \quit_unless  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: PSQL commands: \quit_if, \quit_unless  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers


2016-12-04 17:35 GMT+01:00 Fabien COELHO <coelho@cri.ensmp.fr>:

Hello Pavel,

Some possibilities from pgbench can have sense in psql too - generating
some random numbers from a range.

Could you expand on the use case where this would be useful?

writing test cases
 

In the end we use one parser for psql and for pgbench.

Note that "master" lexer is already shared, thanks to Tom, so as to detect consistently where a query ends.

I agree, so step 2 should be enough, and I accept so there is opened door
for any future enhancing.

Good, because that was the idea:-)

We can implement some client side boolean functions (similar to pgbench
functions that can cover often tasks: version_less, version_greather,
user_exists, tables_exists, index_exists, variable_exists, schema_exists,

Yes, that is a possibility, but this can already be queried into a :-variable, so it is less indispensable.

can you show some examples, please?

Regards

Pavel

 


--
Fabien.

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: PSQL commands: \quit_if, \quit_unless
Next
From: Fabien COELHO
Date:
Subject: Re: PSQL commands: \quit_if, \quit_unless