=?UTF-8?Q?LiuYan_=E5=88=98=E7=A0=94?= <lovetide@21cn.com> writes: > I've also tried add '&charSet=GBK' in the jdbcURL, and got the same result. At a guess, the name of the database will have to be in UTF8. I doubt that JDBC will think it should do any character set conversion on it. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate

Oliver Jowett <oliver@opencloud.com> writes: > Tom Lane wrote: >> At a guess, the name of the database will have to be in UTF8. I doubt >> that JDBC will think it should do any character set conversion on it. > Has something changed here so that non-7-bit data in the startup packet > will work? The server just thinks those are 8-bit strings. I guess my recommendation is that you should go ahead and send UTF8, and if the user created the non-ASCII name that way, it'll work. (In practice I think that means he'd have to issue the CREATE DATABASE or CREATE USER command while logged into a database that uses UTF8 encoding.) This whole business of per-database encodings is a mess, of course. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster