From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [GENERAL] invalid byte sequence ? |
Date: | 2006-08-25 15:30:40 |
Message-ID: | 20060825153040.GJ16535@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Fri, Aug 25, 2006 at 05:07:03PM +0200, Peter Eisentraut wrote:
> I got started on this and just wanted to post an intermediate patch. I have
> taken the logic from initdb and placed it into libpq and refined the API a
> bit. At this point, there should be no behaviorial change. It remains to
> make libpq use this stuff if PGCLIENTENCODING is not set. Unless someone
> beats me, I'll figure that out later.
Umm, why export all these functions. For starters, does this even need
to be in libpq? I wouldn't have thought so the first time round,
especially not three functions. The only thing you need is to take a
locale name and return the charset you can pass to PQsetClientEncoding.
In fact, the only thing you need is PQsetClientEncodingFromLocale(),
anything else is just sugar. Why would the user care about what the OS
calls it? We have a "pg_enc" enum, so lets use it.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2006-08-25 15:38:20 | Re: [GENERAL] invalid byte sequence ? |
Previous Message | Peter Eisentraut | 2006-08-25 15:07:03 | Re: [GENERAL] invalid byte sequence ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew T. O'Connor | 2006-08-25 15:32:02 | Re: Autovacuum on by default? |
Previous Message | Tom Lane | 2006-08-25 15:25:43 | Re: Tricky bugs in concurrent index build |