| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | neilconway(at)home(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Error: "Conversion between UNICODE..." |
| Date: | 2001-07-03 22:55:46 |
| Message-ID: | 26237.994200946@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Neil Conway" <neilconway(at)home(dot)com> writes:
> I'm getting hundreds of errors in my Postgres (7.0.2) logs like this:
> ERROR: Conversion between UNICODE and SQL_ASCII is not supported
> Postgres is compiled without multi-byte support and the encoding on the
> database is SQL_ASCII. AFAIK, there is no need to store UNICODE (but I
> might be wrong -- if that's the problem, tell me).
> Since the database is accessed by hundreds of different clients
> (interfacing using JDBC, PHP4, Perl, and perhaps others), I'm having
> difficulty tracking down where these errors are coming from and why
> they're occuring.
Sounds to me like some of your clients *are* compiled with multibyte
support, and are asking for conversion to Unicode. I'm not an expert
on the multibyte stuff though...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-07-03 22:58:11 | Re: float arrays |
| Previous Message | Tom Lane | 2001-07-03 22:30:53 | Re: OID, 4billion+ Rows. |