Your message dated Wed, 2 Apr 2008 10:40:52 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#471646: mysql connector/j 5.1.6
has caused the Debian Bug report #471646,
regarding libmysql-java: strange SQL Exceptions with Version "5.1.5+dfsg-2:
all"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
471646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471646
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libmysql-java
Version: 5.1.5+dfsg-2
Severity: important
*** Please type your report below this line ***
I'm using the OpenMMS software packet. It's a rdb management
system for crystal protein structures. With the reported
version of libmysql-java i got the following execption:
Load Started Wed Mar 19 10:26:51 CET 2008
Loading PDB_ID: 3b9c
Read time: 1.514 s.
********** LOAD ENTRY FAILED **********
SQL Exception in DBLoader.loadEntries()
while loading Entry PDB_ID=3b9c
Exception Description: java.sql.BatchUpdateException: Data truncation:
Out of range value adjusted for column 'occupancy_esd' at row 1
SQL Message: Data truncation: Out of range value adjusted for
column 'occupancy_esd' at row 1 SQL State: 01004 SQL ErrorCode: 0
Stack Trace
java.sql.BatchUpdateException: Data truncation: Out of range value
adjusted for column 'occupancy_esd' at row 1
at
com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:1669)
at
com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1085)
at
org.rcsb.openmms.dbinsert.InsertEntry.insert_ATOM_SITE(InsertEntry.java:2821)
at
org.rcsb.openmms.dbinsert.InsertEntry.insertEntryData(InsertEntry.java:766)
at
org.rcsb.openmms.apps.rdb.InsertEntryFinal.buildAndInsertEntry(InsertEntryFinal.java:156)
at
org.rcsb.openmms.apps.rdb.DBLoader.insertSingleEntry(DBLoader.java:462)
at
org.rcsb.openmms.apps.rdb.DBLoader.processSingleEntry(DBLoader.java:391)
at
org.rcsb.openmms.apps.rdb.DBLoader.loadSingleEntry(DBLoader.java:265)
at
org.rcsb.openmms.apps.rdb.DBLoader.loadEntries(DBLoader.java:184)
at
org.rcsb.openmms.apps.rdb.PanelSet$LoadManifestButtonObserver$1.construct(PanelSet.java:482)
at
org.rcsb.openmms.apps.rdb.SwingWorker$2.run(SwingWorker.java:111)
at java.lang.Thread.run(Thread.java:595)
********** end of exception report **********
**********************************************************
There is no excpetion with Version: "5.0.4+dfsg-2: all" .
May be its note worthy that i had the same problem former, when i
updated first time from version 3.x to 5.x. A downgrade fixed that problem
that
time , too. It's strange, that the problem now occures again.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libmysql-java depends on:
ii gij-4.1 [java2-runtime] 4.1.2-16 The GNU Java bytecode
interpreter
ii java-gcj-compat [java2-runtim 1.0.77-4 Java runtime environment
using GIJ
ii sun-java5-jre [java2-runtime] 1.5.0-14-3 Sun Java(TM) Runtime
Environment (
libmysql-java recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Apr 01, 2008 at 09:53:25AM -0500, Eric wrote:
> 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.
Thanks for this valuable information. I will close this bug based on
this information. Please reopen if you thing there are still issues.
Cheers,
Michael
--- End Message ---
