Re: pgbench - allow to store select results into variables
От | David G. Johnston |
---|---|
Тема | Re: pgbench - allow to store select results into variables |
Дата | |
Msg-id | CAKFQuwYhDRsStE3gX6AGpk1ZLUcpoXQEN0OFRqcWEd-U6ZuN6w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgbench - allow to store select results into variables (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes:
> On Sat, Jul 9, 2016 at 7:52 AM, Fabien COELHO <coelho@cri.ensmp.fr> wrote:
>> If someone thinks that "gset" is a good idea for pgbench, which I don't, it
>> could be implemented. I think that an "into" feature, like PL/pgSQL & ECPG,
>> makes more sense for scripting.
> I agree: I like \into.
> But:
>> SELECT 1, 2 \; SELECT 3;
>> \into one two three
> I think that's pretty weird.
Yeah, that's seriously nasty action-at-a-distance in my view. I'd be okay
with
SELECT 1, 2 \into one two
SELECT 3 \into three
but I do not think that a metacommand on a following line should
retroactively affect the execution of a prior command, much less commands
before the last one.
You need a test and a definition for:
SELECT 1, 2;
SELECT 3;
\into x, y, z
It should fail - "too many variables" - right?
David J.
В списке pgsql-hackers по дате отправления: