From: | Barry Lind <barry(at)xythos(dot)com> |
---|---|
To: | Culley Harrelson <culleyharrelson(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Fwd: Re: unicode in 7.1 |
Date: | 2001-09-11 23:33:16 |
Message-ID: | 3B9E9F3C.5030502@xythos.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
Culley,
That all looks fine. I don't understand why you would be having
problems with these settings. Are you sure you are using the 7.1 jdbc
drivers? One other thing I can think of to check is to do a 'show
client_encoding'. This should also return UNICODE.
So to restate your problem, you get the 8bit characters returned as ?'s
through jdbc, but it works correctly through psql. Is this a correct
restatement of your problem?
thanks,
--Barry
Culley Harrelson wrote:
>
>
> At 11:45 AM 9/11/01 -0700, you wrote:
>
>> select getdatabaseencoding();
>
>
> UNICODE
>
>> select datname, encoding from pg_database;
>
>
> flashcard | 5
>
> All other databases on the server had 0 for encoding.
>
> Unfortunately my dev environment still has postgres 7.0. I updated my
> connection pool object and it works on dev but not on prod with 7.1. I
> really don't want to update my dev environment untill I can do the whole
> machine from scratch but I fear I might have to in order to debug this...
>
> Culley
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-09-11 23:48:41 | Re: MacOS X Build Fails |
Previous Message | Marko Kreen | 2001-09-11 23:29:25 | Re: Installation location of Perl and Python modules |
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2001-09-12 00:23:40 | Re: Fwd: Re: unicode in 7.1 |
Previous Message | Culley Harrelson | 2001-09-11 19:08:11 | Re: Fwd: Re: unicode in 7.1 |