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:	Windows (Win)
Assigned to:	Mark Matthews	CPU Architecture:	Any

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.

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".

ok, thanks a lot!

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

A note has been added to the 5.0.6 changelog.

Page generated in 0.051 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.