Am 14.07.2011 um 19:40 schrieb David Holt: A quick google around (mysql Data truncation: Data truncated for column) shows it might be a fairly common problem.
Maybe your drivers are different between dev/deploy?
Thanks for that hint!
That was the case. I had an stray MYSQL driver and other stuff lying around in /Library/Java/Extensions on the server. After cleaning up that mess everything worked like a charm!
And I also thank you for your other mail as it provided a sane way to convert our charset mess of a database to UTF-8.
cheers,
Lars
Maybe this provides a work-around?
If you don't want truncation checked for, add 'jdbcCompliantTruncation=false' to your JDBC
url, and the driver will act as Connector/J 3.0 did.
Always a good idea to check the CHANGES file that comes with the driver when upgrading:
"- The driver is more strict about truncation of numerics on
ResultSet.get*(), and will throw a SQLException when truncation is
detected. You can disable this by setting 'jdbcCompliantTruncation' to
false (it is enabled by default, as this functionality is required
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
|