| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | Bernd Helmle <mailings(at)oopsware(dot)de>, Steve Singer <ssinger(at)ca(dot)afilias(dot)info>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: [JDBC] JDBC connections to 9.1 |
| Date: | 2011-04-18 16:12:15 |
| Message-ID: | 23604.1303143135@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Dave Cramer <pg(at)fastcrypt(dot)com> writes:
> On Mon, Apr 18, 2011 at 11:24 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Yeah. I'm thinking what we should do here is revert the change, with a
>> note in the source about why, and also change the JDBC driver to send
>> and expect "UTF8" not "UNICODE" (which as Kevin says is more correct
>> anyway). Then in a few releases' time we can un-revert the server
>> change.
> Well initially my concern was that people would have a challenge in
> the case where they had to re-certify their application if we made
> this change, however I realize they will have to do this anyway since
> upgrading to 9.1 is what necessitates it.
I don't see any backwards compatibility risk, if that's what you mean.
Every backend release since 7.3 has treated client_encoding 'UTF8' and
'UNICODE' the same, and earlier releases didn't accept either one.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-04-18 16:30:22 | Re: switch UNLOGGED to LOGGED |
| Previous Message | Robert Haas | 2011-04-18 15:59:36 | Re: Typed table DDL loose ends |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-04-18 16:35:56 | Re: [JDBC] JDBC connections to 9.1 |
| Previous Message | Dave Cramer | 2011-04-18 15:42:30 | Re: [JDBC] JDBC connections to 9.1 |