| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 16:01:08 |
| Message-ID: | CAMsGm5czKDsvSa91zZVk4YrQsy7yp_Tmf+8W6_KJhcKFxCTw_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 1 Apr 2020 at 11:52, Daniel Verite <daniel(at)manitou-mail(dot)org> wrote:
> 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.
>
I think it might be a good idea to decide whether psql is to be a
programming environment, or just a command shell.
If it is to be a programming environment, we should either adopt an
existing language or strike a committee of programming language experts to
design a new one.
If it is to be a command shell, new features should be evaluated in part on
whether they move psql significantly closer to being a programming language
and rejected if they do.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-04-01 16:02:18 | Re: snapshot too old issues, first around wraparound and then more. |
| Previous Message | Daniel Verite | 2020-04-01 15:52:06 | Re: proposal \gcsv |