Re: Re: [INTERFACES] jdbc: v7.1 bug (letter accent)
От | Jean-Francois Burdet |
---|---|
Тема | Re: Re: [INTERFACES] jdbc: v7.1 bug (letter accent) |
Дата | |
Msg-id | 3A768B42.8BED16AB@adm.unige.ch обсуждение исходный текст |
Ответ на | Re: [INTERFACES] jdbc: v7.1 bug (letter accent) (Barry Lind <barry@xythos.com>) |
Список | pgsql-jdbc |
After doing some search, I found that encoding used for the JDBC connection default to the JVM encoding, so I had add a Property to the connection : info.put("user","fsft"); info.put("password","fsft"); info.put("charSet", "ISO8859_1"); dbCon = DriverManager.getConnection(url,info); And quoted from Barry : > Let me explain a little bit more what is happening here. > In 7.0, the jdbc driver always used the clients default encoding to > convert text returned from the database into java Strings. This > obviously isn't correct when the DB happens to be running with a > different character set than the client. > So in 7.1 the jdbc drivers have been changed to detect the character set > of the database (by making the select getdatabaseencoding(); call). So > if your database was created with the wrong character set (i.e. not > latin1), then this change in behaviour would account for your problem. > Likewise if the database was created with the correct character set, it > should work fine without setting any additional properties. > As you point out, in 7.1 it is also possible to override the character > set used by setting the property you have mentioned below. However this > should not be necessary if the database is created with the correct > character set.
В списке pgsql-jdbc по дате отправления: