David Gagnon wrote:
>> The 'encoding' parameter is only used for connections to pre-7.3
>> servers; in other cases it is ignored.
>
>
> Really?! I must say that this REALLY solved my encoding problem. And I'm
> using 7.4 ?! Without this flag I always get the error describe before.
Hmm -- perhaps the stable driver does things differently. I don't have
that code readily to hand.
Can you try the development driver (without any encoding parameter) and
see if you get different behaviour?
> Do I have to specify something to inform the JDBC driver that it connect
> to a Latin1 database?
You shouldn't need to.
> This statement is read from an sql file. So no prepare statement here
> is the code that cause the problem:
> hasResults = statement.execute(command.toString());
Can you dump out the individual (unicode) character values of 'command'
just to check you're really executing the query you think you are?
-O