From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Chris Angelico <rosuav(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: psql & unix env variables |
Date: | 2012-08-30 23:27:01 |
Message-ID: | 503FF6C5.1080909@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/30/2012 04:19 PM, Chris Angelico wrote:
> On Thu, Aug 30, 2012 at 4:42 PM, Achilleas Mantzios
> <achill(at)smadev(dot)internal(dot)net> wrote:
>> I have found useful the use of variable assignment in psql, e.g.
>>
>> #!/bin/sh
>>
>> # lets say you have some var with a value, or even populate some var with a value from
>> # psql as shown below
>> somevar=`psql -P pager=off -q -t -c "SELECT foo from bar" | head -1 | sed -e 's/ //g'`
>>
>> # now use that variable in psql, (what you want to achieve), but in more tight manner
>> # than simple shell substitution (see -v switch and : notation)
>>
>> psql -P pager=off -q -v somevar=$somevar -c "select foo2 from bar2 where var=:somevar"
>
> At this point, I have to ask: Why not switch to a language with actual
> Postgres bindings? Try Python, or Pike, or something; I'm sure it's
> going to be easier than doing everything through shell scripts.
There is always ShellSQL. Not sure how current it is, but maybe worth a
look:
http://shellsql.sourceforge.net/
>
> ChrisA
>
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2012-08-31 01:37:05 | Re: psql & unix env variables |
Previous Message | Chris Angelico | 2012-08-30 23:19:26 | Re: psql & unix env variables |