Tom Lane wrote:
> Oliver Jowett <oliver(at)opencloud(dot)com> writes:
>> Jeff Davis wrote:
>>> or at least blindly pass the bytes on to the server?
>> What bytes? You have a bunch of UTF-16 characters (possibly with
>> surrogate pairs etc). What encoding do you use to turn that into a
> It wouldn't be entirely unreasonable to define the answer as "UTF-8".
> That would at least provide serviceable behavior to a goodly group of
> users, whereas the current implementation seems guaranteed to fail
> for everyone (other than us ASCII-only Neanderthals who don't care
So then the restriction is "use 7-bit strings, or use a UTF-8 server
encoding"? That sounds reasonable.
How feasible would it be to have the backend transcode user/database
based on the client_encoding given in the StartupMessage? That would
leave authentication as the only remaining wart. It's a pity the current
protocol doesn't allow the backend to emit a ParameterStatus before
authentication is complete ..
In response to
pgsql-jdbc by date
|Next:||From: Steve Foster||Date: 2008-08-04 13:28:34|
|Subject: macaddr data type and prepared statements|
|Previous:||From: Tom Lane||Date: 2008-08-02 04:40:34|
|Subject: Re: Encoding issues |