is the problem reproducable, or occurs it randomly?
The test program I posted produces the error during every run. Does the test program yield an error, if you run it?
If its reproducable, would you mind creating a VTrace? (see http://sapdb.2scale.net/moin.cgi/VTrace on howto do it)
Ok, I will try to do that.
The question is whether the data is already corrupted (that '1' in the number shown in the error message) on server side, or there are some Java quirks that create this (of course not in FIXED(18,8)) number.
Since the getString method seems to give the right result, I would guess that the problem is in the JDBC-driver. I already took a quick look at the java code, but so far I don't understand the code for converting the number from the server answer.
BTW - which locale are you using (as there comes not the right error message out, and there should be english messages in this case ...)
I compiled this driver from the source, and I forgot to include the messages.properties in in the jar file. By the way, the version of the source that I used is:
Implementation-Version: 7.4.4 Build 001-000-156-985
Thanks,
Thomas Rohwer
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
