| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | kenr(at)redergaard-it(dot)no |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Problems with JDBC client and LATIN1 chars |
| Date: | 2004-03-10 00:06:13 |
| Message-ID: | Pine.BSO.4.56.0403091902390.32046@leary.csoft.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Thu, 4 Mar 2004 kenr(at)redergaard-it(dot)no wrote:
> Hi,
>
> I'm experiencing a decoding problem with PG 7.3.4 and the latest
> Postgresql JDBC driver.
>
> When transfering the Norwegian letters øæå the JDBC driver claims that
> illegal chars are received. But when using pgAdmin this works fine.
>
> Are there any patches available to get pgAdmin behaviour (accepting LATIN1) ?
pgAdmin is one of the many pg clients that are in the "ignorance is bliss"
category. Java needs your encoding to be correct.
> Or do I have to pgdump, stop the production environment, alter the cluster
> to use LATIN1, and pgrestore the db ? I really hope that there is another
> way to do this...
>
Sorry, no.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2004-03-10 00:11:01 | Re: About use SSL by JDBC |
| Previous Message | Kris Jurka | 2004-03-09 18:28:22 | Re: is nullable working? |