| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | smota <samuelmota(at)gmail(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Charset problem on WHERE clause |
| Date: | 2004-07-26 17:09:09 |
| Message-ID: | Pine.BSO.4.56.0407261205440.7379@leary.csoft.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 26 Jul 2004, smota wrote:
> Hi,
>
> I'm pretty new to PostgreSQL as well to it's JDBC driver.
>
> For now I'm using PostgreSQL 7.3.6 version under Red Hat ES 3.0.
> The database is created with SQL_ASCII encoding.
> I'm retriving data from the database with the pg74.214.jdbc3.jar driver.
>
> jdbc:postgresql://10.100.1.11:5432/mydatabase?charSet=LATIN1
You should not use a SQL_ASCII database. The JDBC driver requires you
database to use a proper encoding for your data. The ?charSet url
parameter was designed to work around this problem for <= 7.2 servers
which didn't come with multibyte encoding support compiled by default, but
it is ignored in => 7.3 servers so it is useless here.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2004-07-26 17:11:50 | Re: conflict txns in serialization isolation |
| Previous Message | Ian Pilcher | 2004-07-26 16:42:23 | Re: Problem w/ IDENT authentication |