MySQL JDBC 5.0.5 bug with TIME column and midnight

Posted At : March 21, 2008 7:24 PM
Related Categories: Web Dev

Coldfusion 8 comes bundled with the mysql commercial jdbc driver 5.0.5 (or it did with my install anyway). I just ran into a bug that results in this error: java.sql.SQLException: Value '00:00:00 can not be represented as java.sql.Time

The bug is the date / time parsing interprets midnight (00:00:00) as illegal for the TIME type.

Two ways to fix.

Update to 5.0.6 (I haven't tried this yet, but assume it would be just fine)

OR add "useFastDateParsing=false" to the connection string in the datasource.

I tried the "useFastDateParsing=false" and it worked perfectly. No restarts of anything. Not sure how that will affect performance though. My quick tests show it running pretty quick still. If I get time I will try with and without and time queries to see. Ideally I would like to update the driver instead, but its Friday at 5:30 and I am not about to do that right now.

Which gets me thinking, how often would Adobe be updating these drivers? Will the next updater fix this? Or should we be doing that manually?

Comments (5) |

Print |

del.icio.us |

Digg It! | 4634 Views

TweetBacks

Comments (Comment Moderation is enabled. Your comment will not appear until approved.)

[Add Comment] [Subscribe to Comments]

Thanks so much for this post. I had the same problem even though the CF8 upgrade migrated my CF7 "manually created" j connector. Not surprisingly, the "useFastDateParsing=false" didn't work on the old Datasources, but recreating them using the native CF8 MySQL 4/5 datatype with the "useFastDateParsing=false" connection string worked like a champ.

# Posted By Dan | 4/14/08 6:31 PM

Thanks! I had the same Coldfusion "java.sql.SQLException: Value '00:00:00 can not be represented as java.sql.Time" issue. Adding useFastDateParsing=false under the connection string in the advanced settings of the data source in the administrator fixed it. Granted, it doesn't address the larger issue with my CFAdmin having a bug, but for now my web app works again.

# Posted By MikeL | 9/25/09 2:50 PM

Hey thanks!! Had the same issue. useFastDateParsing=false is just sweet!!

# Posted By Angel B. | 1/21/10 11:31 PM

Thanks for the post, problem is resolved with the mysql driver update. but i didn't understand where i need to use the "useFastDateParsing=false", presently i'm using the datasource connection of commons-dbcp connection pooling BasicDataSource, it is not accepting because there is no getter/setter method for the property of useFastDateParsing. can any one help me to resolve the problem using this property.

# Posted By Sudhakar | 11/26/10 3:17 AM

Thank You, Thank You, Thank You! I was losing my mind as to what could be wrong with my code since everything was query paramed until i ran across this.