Re: csv format for psql
Pavel Stehule <pavel.stehule@gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Daniel Verite <daniel@manitou-mail.org>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>,
Isaac Morland <isaac.morland@gmail.com>, "David G. Johnston" <david.g.johnston@gmail.com>,
David Steele <david@pgmasters.net>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2018-04-07T12:00:52Z
Lists: pgsql-hackers
2018-04-07 13:55 GMT+02:00 Daniel Verite <daniel@manitou-mail.org>: > Pavel Stehule wrote: > > > so we can to have > > > > \pset format xxx > > > > and set of local possibly changed defaults > > > > \pset csv_fieldsep , > > \pset csv_tuplesonly on > > \pset unaligned_fieldsep | > > \pset unaligned_tuplesonly off > > tuples_only (\t) is a single setting that is currently used by all > formats. It makes sense as it is and I don't quite see what we > would gain by "exploding" it. > It was a example, how the one default can be not good enough. Usually we expect in align, unalign headers by default. But somebody can expect tuples only by default for CSV format. > There's also "footer" that goes in tandem with "tuples_only", > to switch off the footer while keeping the header and title. > Whatever change is considered to "tuples_only", "footer" must > be considered with it. > For the csv format, tuples_only=off is interpreted as "output the header" > and tuples_only=on as "don't output the header". This is consistent > with what other formats do. > My note was not about the implementations, it was about different expectations of some users - looks on Isaac's mail, pls. > > > Best regards, > -- > Daniel Vérité > PostgreSQL-powered mailer: http://www.manitou-mail.org > Twitter: @DanielVerite >
Commits
-
Add CSV table output mode in psql.
- aa2ba50c2c13 12.0 landed
-
Reorganize format options of psql in alphabetical order
- add9182e5908 12.0 landed
-
Complete TODO item:
- 862b20b38228 8.0.0 cited