| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Encoding issues |
| Date: | 2008-09-19 22:55:08 |
| Message-ID: | Pine.BSO.4.64.0809191852350.32123@leary.csoft.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Sat, 2 Aug 2008, Tom Lane wrote:
> 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
> anyway...)
>
I've committed a change to the driver to send all initial startup data in
UTF-8. It wouldn't be tough to expose this as a URL parameter for
initialConnectionEncoding because I've refactored the encoding decisions
out of UnixCrypt and MD5Digest. I haven't done that at this point because
I'm lazy and I'm not sure how many people actually need such a feature.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2008-09-19 23:45:59 | Re: Postgresql JDBC UTF8 Conversion Throughput |
| Previous Message | Paul Lindner | 2008-09-19 18:36:13 | Re: Postgresql JDBC UTF8 Conversion Throughput |