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
Ack! I guess I am hitting this problem
I had my database rebuilt to use UNICODE encoding. Data now appears
correctly in pgsql but not when filtered through JDBC. Unfortunately Im
using the open source DbConnectionBroker connection pooling object and I
have to dig into this to apply the
Culley,
With out more details of your setup, I can't give you a complete answer.
But check out the info at:
http://lab.applinet.nl/postgresql-jdbc/#CharacterEncoding
for a brief discussion of what I believe is your problem. There has
also been a number of discussions on this on the pgsql-j
> 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
The was corrupted in the process of the upgrade.
Is there some way to tell what the configuration options were when it was
installed? I am assuming by API you mean how am I accessing Postgres? JDBC.
Culley
>X-Apparently-To: [EMAIL PROTECTED] via web9605; 10 Sep 2001
>18:19:26 -0700 (PDT)
>
