| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Vik Fearing" <vik(at)postgresfriends(dot)org>,"Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>,"Erik Rijkers" <er(at)xs4all(dot)nl>,"PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal \gcsv |
| Date: | 2020-04-01 15:52:06 |
| Message-ID: | 8090710a-81cf-4a9e-9067-60ebe917cb8e@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> I could see having a command to copy the current primary formatting
> parameters to the alternate area, too.
We could have a stack to store parameters before temporary
changes, for instance if you want to do one csv export and
come back to normal without assuming what "normal"
values were.
\pset push format csv_fieldsep
\pset format csv
\pset csv_fielsep '\t'
some command \g somefile
\pset pop
So \pset pop would reset the pushed parameters
to their values when pushed, which also could be all
parameters:
\pset push all
\pset param1 something
\pset param2 something-else
...other commands...
\pset pop
or
\pset push all
\i somescript.sql
\pset pop
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Isaac Morland | 2020-04-01 16:01:08 | Re: proposal \gcsv |
| Previous Message | David Steele | 2020-04-01 15:43:45 | Re: BufFileRead() error signalling |