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 CAFj8pRBctV3imQ4KM1KVqK1BnVF1_=djLHPY0cMNMsXCqH8a7A@mail.gmail.com
Whole thread Raw
In response to Re: proposal - assign result of query to psql variable  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
2013/2/3 Tom Lane <tgl@sss.pgh.pa.us>:
> Pavel Stehule <pavel.stehule@gmail.com> writes:
>> now missing variables is replaced by variable's name. We can implement
>> some pset option - some like define what do with missing variable
>
>> \pset missing_variable (use_name | use_null | error )
>
> No, it isn't "replaced by variable's name".  What actually happens is we
> don't attempt a replacement unless the string after the colon matches an
> existing variable.  Tampering with that seems dangerous and foolish.

some other ideas?

do you think so full NULL support has sense?

Regards

Pavel

>
>                         regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: proposal - assign result of query to psql variable
Next
From: Jeff Janes
Date:
Subject: Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system