| From: | Denis Bucher <dbucher(at)niftycom(dot)com> |
|---|---|
| To: | Rene Pijlman <rene(at)lab(dot)applinet(dot)nl> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Accents bug ? |
| Date: | 2001-10-02 10:14:35 |
| Message-ID: | 5.1.0.14.0.20011002120708.0242fa90@mail.niftycom.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
At 11:48 02.10.01 +0200, Rene Pijlman wrote:
Hello !
> >It sounds like an encoding problem. You can check the encoding of the db
> >by using \encoding in psql.
> >There is a section in the docs on this
> >http://www.postgresql.org/idocs/index.php?multibyte.html
>
>And more on
>http://lab.applinet.nl/postgresql-jdbc/#CharacterEncoding
Yes, very interesting, it says :
jdbc:postgresql://localhost/dbname?charSet=UTF-8&user=foo&password=bar
But it gives me an error using that connection string :
>
jdbc:postgresql://sashimi:5432/ekai?charSet=UNICODE&user=ekaitest&password=aaa
...when doing my executeQuery I get :
> VendorError: 0
> SQLState: null
> SQLException: postgresql.con.encoding
So, not better... or is it really "UNICODE" ?
>I've heard of conversion problems before, but not of chunking
>the data though.
Yes, that's the most strange I think :-)
Denis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Grant Edwards | 2001-10-02 11:44:22 | Errors when building jdbc dirver jar file |
| Previous Message | Rene Pijlman | 2001-10-02 09:48:12 | Re: Accents bug ? |