Problems with TimeSpan columns that exceeds 24 hours

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
Marcel_NL
Posts: 3
Joined: Fri 25 Jul 2008 07:38

Problems with TimeSpan columns that exceeds 24 hours

Post by Marcel_NL » 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.
Top
AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Tue 29 Jul 2008 13:40

The problem is fixed now. Look forward for the next build.
Top
Post Reply

Return to “dotConnect for MySQL”