From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tony Grant <tony(at)animaproductions(dot)com> |
Cc: | Barry Lind <barry(at)xythos(dot)com>, Jani Averbach <jaa(at)cc(dot)jyu(dot)fi>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |
Date: | 2001-05-04 15:40:48 |
Message-ID: | 25419.988990848@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Tony Grant <tony(at)animaproductions(dot)com> writes:
> On 04 May 2001 10:29:50 -0400, Tom Lane wrote:
>> Does this happen with a non-multibyte-compiled database? If so, I'd
>> argue that's a serious bug in the JDBC code: it makes JDBC unusable
>> for non-ASCII 8-bit character sets, unless one puts up with the overhead
>> of MULTIBYTE support.
> I fought with this for a few days. The solution is to dump the database
> and create a new database with the correct encoding.
> MULTIBYTE is not neccesary I just set the type to LATIN1 and it works
> fine.
But a non-MULTIBYTE backend doesn't even have the concept of "setting
the encoding" --- it will always just report SQL_ASCII.
Perhaps what this really says is that it'd be better if the JDBC code
assumed LATIN1 translations when the backend claims SQL_ASCII.
Certainly, translating all high-bit-set characters to '?' is about as
uselessly obstructionist a policy as I can think of...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Grant | 2001-05-04 15:58:41 | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |
Previous Message | Tony Grant | 2001-05-04 15:36:07 | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Grant | 2001-05-04 15:58:41 | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |
Previous Message | Tony Grant | 2001-05-04 15:36:07 | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |