Richard Wesley wrote:
Hey Sjoerd -
On 13 Oct 2008, at 14:19, Sjoerd Mullender wrote:
Conversions happen because the interface to the server uses UTF-8 and often the interface from the application to the driver (actually, the interface between the driver manager and the driver) uses wide characters (i.e. UTF-16). But I would be interested in fixing any bugs in that area, so if you can capture a log session where it goes wrong, I'd be grateful.
I'll try to get some output for you.
How is this?
Beautiful. Your log forced me to take another close look at the code, and I think I found a bug that could explain the UTF-16 problem. Basically it is a matter of looking beyond the end of the string being converted to UTF-16 (internally the driver uses UTF-8, but since your application uses wide-character calls, result strings need to be converted). I think I nailed this bug, so I will commit this to our repository shortly. As to your question about6 the generic error, the driver often returns a generic error because a query was not acceptable to the server and the driver doesn't interpret the error messages that come back from the server (they are too varied and unstructured). So the best the driver can do is give a generic error. -- Sjoerd Mullender