22 Nov
2007
22 Nov
'07
8:29 p.m.
On 22-11-2007 21:20:50 +0100, Markus Gritsch wrote:
On Nov 22, 2007 8:52 PM, Fabian Groffen
wrote: Also, it would help us very much if you could generate a JDBC debug log when this happens. You can make such log by appending ?debug=true to the JDBC connection url.
The attached logs show running this statement:
UPDATE sys.test SET name = 'รค' WHERE id = 0
Your logs actually show you don't even get to the tricky part: TD 1195762741893: write final block: 53 bytes TX 1195762741893: sPREPARE UPDATE sys.test SET name = '?' WHERE id = 0; RD 1195762741893: read final block: 25 bytes RX 1195762741893: !unexpected end of input The server aparently doesn't like this prepare statement. Niels, any idea on this?