Re: proposal - assign result of query to psql variable
David Fetter <david@fetter.org>
From: David Fetter <david@fetter.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2012-07-26T06:19:55Z
Lists: pgsql-hackers
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... 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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix oversight in new code for printing rangetable aliases.
- 8b728e5c6e0c 9.3.0 cited