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
Have a nice day,
Martijn van Oosterhout <kleptog(at)svana(dot)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.
In response to
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2006-02-10 19:01:13|
|Subject: pgsql: Change search for default operator classes so that it examines |
|Previous:||From: Martijn van Oosterhout||Date: 2006-02-10 17:16:07|
|Subject: Re: [COMMITTERS] pgsql: Allow psql multi-line column values to align|
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2006-02-10 19:04:29|
|Subject: Re: Scrollable cursors and Sort performance |
|Previous:||From: Martijn van Oosterhout||Date: 2006-02-10 18:14:12|
|Subject: Re: Scrollable cursors and Sort performance|