Re: [COMMITTERS] pgsql: Allow psql multi-line column values to align - Mailing list pgsql-patches

From Martijn van Oosterhout
Subject Re: [COMMITTERS] pgsql: Allow psql multi-line column values to align
Date
Msg-id 20060210184349.GE576@svana.org
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Allow psql multi-line column values to align  (Martijn van Oosterhout <kleptog@svana.org>)
Responses Re: [COMMITTERS] pgsql: Allow psql multi-line column values to align  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Fri, Feb 10, 2006 at 06:16:07PM +0100, Martijn van Oosterhout wrote:
> Thanks for the tip. I'm currently merging CVS with my version and
> getting a lot of conflicts (whitespace variations).
>
> It's fairly simple changes AFAICS. Just need to fix the declarations of
> a few variables.

Does PostgreSQL have a policy on the signedness of strings? When I was
making the patch I generally used "unsigned char" to try to emphasise
that these are not characters, they are bytes of an encoding. But this
doesn't play well with existing functions like PQdsplen and PQmblen.

At this point I'm thinking of dropping the "unsigned" everywhere and
just being really careful of comparisons. OTOH, it's really those two
functions being inconsistant because the underlying functions do use
unsigned. Thoughts?

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.

pgsql-patches by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: [COMMITTERS] pgsql: Allow psql multi-line column values to align
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Allow psql multi-line column values to align