Re: encoding problems - Mailing list pgsql-novice

From Cliff Nieuwenhuis
Subject Re: encoding problems
Date
Msg-id 200803111407.40621.cliff@nieusite.com
Whole thread Raw
In response to Re: encoding problems  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-novice
On Tuesday 11 March 2008 11:41:35 Tom Lane wrote:
> Cliff Nieuwenhuis <cliff@nieusite.com> writes:
> > I'm not sure how to ask this question.  I have written a function, and
> > with PostgreSQL 8.0.13 I can do a "\df+" and see something like this
> > under Source Code:
> >     DECLARE
> >         result text;
> > ...
> >
> > If I create the same function on my computer running PostgreSQL 8.3.0 and
> > try the \df+ then the Source Code shows:
> >
> > \x09DECLARE
> > \x09\x09result text;
> > ...
>
> That's not an encoding problem, that's an intentional behavioral change
> in the way that psql formats strings for display.
>
> I guess it's a bit annoying if you were hoping that tabs would be useful
> for pretty-printing purposes.  Should we reconsider what's done with a
> tab in mbprint.c?
>
>             regards, tom lane

My vote would be to go back to the old way, or at least have that as an option
of some sort.  I use command-line psql all the time -- to me, psql offers the
same advantages as using a command-line interface for other work. I find the
extra characters really get in the way.

Thanks for the prompt reply!

--
Cliff

pgsql-novice by date:

Previous
From: Joshua
Date:
Subject: simple question concerning plpgsql and SQL Functions
Next
From: Cliff Nieuwenhuis
Date:
Subject: Re: [HACKERS] encoding problems