Re: Field Separator setting not used.

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: kevin(dot)colagio(at)usa(dot)xerox(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Field Separator setting not used.
Date: 2000-10-17 21:06:05
Message-ID: Pine.LNX.4.21.0010172302300.9649-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

pgsql-bugs(at)postgresql(dot)org writes:

> psql -t -q -d servicedesk -F '###' -c "select * from users"
>
> The output should be along the lines of:
>
> abc123###Kevin###Colagio###820###209###x56469
>
> Which is then parsed by a perl program...but instead, it comes up as:
>
> abc123 | Kevin | Colagio | 820 | 209 | x56469

You need to set the output mode to unaligned, e.g., using the -A option.

Quoth the documentation:

\pset parameter [ value ]

...
format Sets the output format to one of unaligned,
aligned, html, or latex. Unique abbrevia­
tions are allowed. (That would mean one let­
ter is enough.)

``Unaligned'' writes all fields of a tuple
on a line, separated by the currently active
field separator. This is intended to create
output that might be intended to be read in
by other programs (tab-separated, comma-sep­
arated).
...
fieldsep
Specifies the field separator to be used in
unaligned output mode. That way one can cre­
ate, for example, tab- or comma-separated
output, which other programs might prefer.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2000-10-18 03:40:44 Re: Bugs in to_char function
Previous Message Nishad Prakash 2000-10-17 20:51:09 Re: UPPER and LOWER dosen't work correctly on special caracters (umlauts)