If you are getting a parse error as you said in a latter message, then
you should set "debug_print_query = true" in your postgresql.conf file.
This will cause the sql statements to be printed in the server log
file and you then might be able to figure out why the statement sent
couldn't be p
es? JDBC.
>>Culley
>>
>>>X-Apparently-To: [EMAIL PROTECTED] via web9605; 10 Sep 2001
>>>18:19:26 -0700 (PDT)
>>>X-Track: 1: 40
>>>To: [EMAIL PROTECTED]
>>>Cc: [EMAIL PROTECTED]
>>>Subject: Re: [GENERAL] unicode in 7.1
>>>X-Mai
you mean how am I accessing
> Postgres? JDBC.
>
> Culley
>
>
>> X-Apparently-To: [EMAIL PROTECTED] via web9605; 10 Sep 2001
>> 18:19:26 -0700 (PDT)
>> X-Track: 1: 40
>> To: [EMAIL PROTECTED]
>> Cc: [EMAIL PROTECTED]
>> Subject: Re: [GENERAL] uni
> The was corrupted in the process of the upgrade.
>
> Is there some way to tell what the configuration options were when it was
> installed?
pg_config --configure
> I am assuming by API you mean how am I accessing Postgres? JDBC.
7.1's JDBC driver has been slightly enhanced from 7.0 in the
0 (PDT)
>X-Track: 1: 40
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: [GENERAL] unicode in 7.1
>X-Mailer: Mew version 1.94.2 on Emacs 20.7 / Mule 4.1
> =?iso-2022-jp?B?KBskQjAqGyhCKQ==?=
>Date: Tue, 11 Sep 2001 10:19:00 +0900
>From: Tatsuo Ishii <[EMAIL
> my isp recently upgraded form postgreSQL 7.0 to 7.1. It went pretty well
> but I just discovered that non-english characters are now in the database
> as a question mark-- inserting non-english characters produces a ? as
> well. Any idea what has gone wrong and what we need to do to fix this?
> my isp recently upgraded form postgreSQL 7.0 to 7.1. It went pretty well
> but I just discovered that non-english characters are now in the database
> as a question mark-- inserting non-english characters produces a ? as
> well. Any idea what has gone wrong and what we need to do to fix this?
Hello,
my isp recently upgraded form postgreSQL 7.0 to 7.1. It went pretty well
but I just discovered that non-english characters are now in the database
as a question mark-- inserting non-english characters produces a ? as
well. Any idea what has gone wrong and what we need to do to fix this?
