From: | Rob Resendez <resendez(dot)java(at)gmail(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | jdbc-4.1 v42.0.0 - set client_encoding |
Date: | 2017-03-16 20:21:07 |
Message-ID: | CAOfv7YcgExpLi3MrUi54=_aA3k1=0wobXDoYMjq_D7=G1WdxVA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
jdbc-4.1 v42.0.0
Our database enoding is "SQL_ASCII". JDBC's client_encoding is "UTF-8"
We're making the leap from pg9.2 to 9.6... and existing code has started
throwing exceptions:
"invalid byte sequence for encoding "UTF8"..."
Per this thread:
https://www.postgresql.org/message-id/55CA237A.4080300@nqadmin.com
"9.4 is intentionally less lax about that than prior versions" (regarding
character data not supported by the client encoding)
We've decided to force the JDBC client_encoding to "SQL_ASCII". Per the
docs, "allowEncodingChanges" will allow "SET client_encoding..." execution;
However, I'm wondering if there is a way to force the connection to use a
particular encoding to begin with?
I've tried "props.setProperty('client_encoding', ...)" without success.
Thanks
From | Date | Subject | |
---|---|---|---|
Next Message | Jorge Solórzano | 2017-03-16 22:02:52 | Re: jdbc-4.1 v42.0.0 - set client_encoding |
Previous Message | Dave Cramer | 2017-03-16 09:47:51 | Re: How not to use JDBC (JDBC Performance Scale 15x presentation) |