Skip site navigation (1) Skip section navigation (2)

Re: Unicode UTF-8 table formatting for psql text output

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Roger Leigh <rleigh(at)codelibre(dot)net>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Unicode UTF-8 table formatting for psql text output
Date: 2009-10-31 19:27:39
Message-ID: 4AEC8FAB.5020509@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackers

Roger Leigh wrote:
> On Sat, Oct 31, 2009 at 12:25:22PM -0400, Andrew Dunstan wrote:
>   
>> Roger Leigh wrote:
>>     
>>> Wouldn't it be much simpler all around to add a "csv" output format
>>> in addition to the above for this purpose?  Spreadsheets can read
>>> it in with no trouble at all.
>>>       
>> We've had CSV output since version 8.0.
>>     
>
> Really?  The only references I see are in tab-complete.c relating to
> COPY.
>
> You can set the field separator to ',' but you can't do a
>   \pset format csv
> and get CSV with correct quoting, escaping etc AFAICS.  It'll
> still break on line wrapping if wrapping is enabled, and with
> newlines in the data.
>
> If that would be a useful addition, I can add it.
>
>
>
>   

It's done by the backend, not by psql, but it has psql support - see \copy

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Marko KreenDate: 2009-10-31 20:45:29
Subject: Re: Weird PL/Python elog output
Previous:From: Tom LaneDate: 2009-10-31 18:59:58
Subject: Re: Patch set under development to add usage reporting.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group