mysql connector/j 5.1.6
A "Data truncation" exception is not necessarily strange. I imagine
this OpenMMS package is indeed inserting an out of range value and the
bug is there. There were some bugs w/ Connector/j not correctly
complaining about out-of-range values that I believe were solved
between 5.0 and 5.1, which would explain why you haven't seen it until
now. I imagine it would go away if you turned off if you set
jdbcCompliantTruncation=false in your connection URL, although that
won't solve the underlying (potential) problem.
On Tue, Apr 01, 2008 at 04:43:04PM +0200, Michael Koch wrote:
> On Tue, Apr 01, 2008 at 09:11:14AM -0500, Eric wrote:
> > Any word on this? Anything I can do?
> When you can give input on bug #471646 that would be great. I can't
> reproduce this currently.
> To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org
To UNSUBSCRIBE, email to debian-java-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com