Bug #26789 a_resultset.getTime(a_column) throws exception when reading 00:00:00
Submitted: 2 Mar 2007 8:35 Modified: 13 Apr 2007 8:33
Reporter: Mario Piver Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / J Severity:S2 (Serious)
Version:Connector/J 5.0.5, MySQL 5.0.27 OS:Microsoft Windows (Win)
Assigned to: Mark Matthews CPU Architecture:Any

[2 Mar 2007 8:35] Mario Piver
Description:
I am filling columns of type TIME with 00:00:00, at some point
in my application when that specific data is not yet available.
When trying to read that with the new Connector/J 5.0.5 
java.sql.Time getTime(String), an exception
is thrown. This didn't happen with 5.0.4.
I'd like to keep the previous behaviour if possible...

How to repeat:
Fill a TIME type column with 00:00:00 and then use
java.sql.Time getTime(String) on it.
[2 Mar 2007 19:27] Mark Matthews
This is a bug in the new fast time parsing code (it's too aggressive at finding "all zero" dates). 

Until it's fixed, the workaround is to configure the driver with "useFastDateParsing=false".
[3 Mar 2007 5:37] Mario Piver
ok, thanks a lot!
[21 Mar 2007 20:01] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/22533
[13 Apr 2007 8:33] MC Brown
A note has been added to the 5.0.6 changelog.