| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Barry Lind <barry(at)xythos(dot)com> |
| Cc: | 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 14:29:50 |
| Message-ID: | 24851.988986590@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Barry Lind <barry(at)xythos(dot)com> writes:
> With regards to your specific problem, my guess is that you haven't
> created you database with the proper character set for the data you are
> storing in it. I am guessing you simply used the default SQL Acsii
> character set for your created database and therefore only the first 127
> characters are defined. Any characters above 127 will be returned by
> java as ?'s.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-05-04 14:36:32 | Re: Packaging 7.1.1 |
| Previous Message | Roland Roberts | 2001-05-04 14:24:53 | Re: Re: New Linux xfs/reiser file systems |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Grant | 2001-05-04 15:36:07 | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |
| Previous Message | Travis Bauer | 2001-05-04 11:45:56 | Re: How to encode and decode a string as a password field in pgsql table? |