On 22-11-2007 22:58:43 +0100, Markus Gritsch wrote:
On Nov 22, 2007 10:54 PM, Fabian Groffen
wrote: Can you try the same query but with a normal character and check if it works?
Of course I have already tried this :) It works fine, as you can see from the attached logfiles.
TX 1195768551757: sPREPARE UPDATE sys.test SET name = 'ok' WHERE id = 0; Ok, so that means the ? is actually the char that you try to insert, and there is a problem somewhere early in the stack to map this char into something useful, whereas it appears to be sent to the server, which just thinks it sees an EOF/invalid escape sequence. The fact that you have a ? on your disk (are you sure about that? How do you open up the file?) means that Java already couldn't map the character to something correct. It is a bug for us to make sure the server responds correctly. It is a bug for an yet to determine party why the LATIN-1 char you insert (most probably, as you're in the windows world) isn't mapped correctly into an utf-8 char. It seems like Java is to blame here, but on the other hand... we explicitly request UTF-8 streams, and Java internally is UTF-16, so it is hard to believe that Sun didn't test this on Windows...