Re: proposal - assign result of query to psql variable - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal - assign result of query to psql variable
Date
Msg-id CAFj8pRCMBr4-9k76bEi-pra-3haBHRiBZfjFcdoxDNSsOqZ1bA@mail.gmail.com
Whole thread Raw
In response to Re: proposal - assign result of query to psql variable  (David Fetter <david@fetter.org>)
Responses Re: proposal - assign result of query to psql variable
List pgsql-hackers
2012/7/26 David Fetter <david@fetter.org>:
> On Thu, Jul 26, 2012 at 01:36:17AM -0400, Tom Lane wrote:
>> Pavel Stehule <pavel.stehule@gmail.com> writes:
>> > \eset variable [, variable [..]] query --  it raise exception when
>> > more than one row is returned or when no row is returned
>>
>> Better would be a variant on \g, that is you type in the query and
>> then tell it where to put the result.  We have learned the hard way
>> that putting SQL commands into the arguments of backslash commands
>> is a horrid idea.  Maybe
>>
>>       select x,y,... from ...
>>       \gset var1 var2 ...
>
> How about
>
> \gset var1,,,var2,var3...
>

I don't like this - you can use fake variable - and ignoring some
variable has no big effect on client

Pavel


> The above shows how one would skip assigning variables in the target
> list, which one might want to do.
>
> Cheers,
> David.
> --
> David Fetter <david@fetter.org> http://fetter.org/
> Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
> Skype: davidfetter      XMPP: david.fetter@gmail.com
> iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
>
> Remember to vote!
> Consider donating to Postgres: http://www.postgresql.org/about/donate


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: proposal - assign result of query to psql variable
Next
From: David Fetter
Date:
Subject: Re: proposal - assign result of query to psql variable