From: Andrew Dunstan on


Tom Lane wrote:
> regression=# select E'xxxxxxx\nxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\nxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
> as a, 1 as b;
> a | b
> ------------------------------------------------------+---
> xxxxxxx +| 1
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx +|
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
> (1 row)
>
> regression=#
>
> The point here is exactly that previous versions didn't show the
> distinction well.
>
>
>

If we really want to make linefeeds visible, I think we should place the
indicators immediately after the character preceding the line feed, not
next to the column separator.

cheers

andrew

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Tom Lane on
Andrew Dunstan <andrew(a)dunslane.net> writes:
> If we really want to make linefeeds visible, I think we should place the
> indicators immediately after the character preceding the line feed, not
> next to the column separator.

Then it's hard to tell it apart from an instance of that character in
the data.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Andrew Dunstan on


Tom Lane wrote:
> Andrew Dunstan <andrew(a)dunslane.net> writes:
>
>> If we really want to make linefeeds visible, I think we should place the
>> indicators immediately after the character preceding the line feed, not
>> next to the column separator.
>>
>
> Then it's hard to tell it apart from an instance of that character in
> the data.
>
>
>

Yeah, I just thought of that. Oh, well, old-ascii for me ;-)

cheers

andrew

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Bruce Momjian on
Andrew Dunstan wrote:
>
>
> Tom Lane wrote:
> > regression=# select E'xxxxxxx\nxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\nxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
> > as a, 1 as b;
> > a | b
> > ------------------------------------------------------+---
> > xxxxxxx +| 1
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx +|
> > xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
> > (1 row)
> >
> > regression=#
> >
> > The point here is exactly that previous versions didn't show the
> > distinction well.
> >
> >
> >
>
> If we really want to make linefeeds visible, I think we should place the
> indicators immediately after the character preceding the line feed, not
> next to the column separator.

One idea would be to change the column _separator_ for newlines --- that
way, they don't show up for single-column output.

--
Bruce Momjian <bruce(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Robert Haas on
On Thu, Dec 10, 2009 at 8:11 PM, Bruce Momjian <bruce(a)momjian.us> wrote:
> Andrew Dunstan wrote:
>>
>>
>> Tom Lane wrote:
>> > regression=# select E'xxxxxxx\nxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\nxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
>> >     as a, 1 as b;
>> >                           a                           | b
>> > ------------------------------------------------------+---
>> >  xxxxxxx                                             +| 1
>> >  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx                  +|
>> >  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
>> > (1 row)
>> >
>> > regression=#
>> >
>> > The point here is exactly that previous versions didn't show the
>> > distinction well.
>> >
>> >
>> >
>>
>> If we really want to make linefeeds visible, I think we should place the
>> indicators immediately after the character preceding the line feed, not
>> next to the column separator.
>
> One idea would be to change the column _separator_ for newlines --- that
> way, they don't show up for single-column output.

Hilariously enough, that's exactly what we used to do. I am leaning
toward the view that we should revert all the ASCII output format
changes vs. 8.4 and let people use the new unicode mode if they want
all the spiffy bells and whistles.

....Robert

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers