Problems with TimeSpan columns that exceeds 24 hours
Posted: Fri 25 Jul 2008 07:54
While saving a TimeSpan value of 40 hours (string value of “1.16:00:00”) MySql or the CrLabs drivers truncate the day part and only saves 16:00:00 in the TIME column. I don’t want ending up saving seconds, converting them back to a TimeSpan and visa versa.
We currently use MySQL direct 3.55.25.0. I know that this isn’t the latest version but I like to know if an update is relevant for this problem before I purpose a new an update.
We currently use MySQL direct 3.55.25.0. I know that this isn’t the latest version but I like to know if an update is relevant for this problem before I purpose a new an update.