Bug #73788 | Unable to use DateTimeOffset in code-first EF model with MySQL Connector for .NE | ||
---|---|---|---|
Submitted: | 3 Sep 2014 4:11 | Modified: | 16 Dec 2014 10:13 |
Reporter: | J Crim | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | Connector / NET | Severity: | S2 (Serious) |
Version: | 6.8.3.2, 6.9.5 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | DateTimeOffset, EF |
[3 Sep 2014 4:11]
J Crim
[3 Sep 2014 4:15]
J Crim
Zip file containing the solution with xunit test cases.
Attachment: MySqlConnNetBugs.zip (application/x-zip-compressed, text), 9.35 KiB.
[16 Dec 2014 10:13]
Chiranjeevi Battula
Hello J Crim, Thank you for the bug report. Verified this behavior on Visual Studio 2013 (C#.Net) with MySQL Connector/Net 6.9.5. Thanks, Chiranjeevi.
[8 Jul 2015 20:00]
Eduardo Rivera
I have a problem and i think is related to this bug. My Mysql-databse has a table with a timestamp column that is mapped to a System.DateTime, and it should be mapped to DateTimeOffset type. How can i handle this?. Thanks.
[8 Jul 2015 20:01]
Eduardo Rivera
By the way, i have Connector 6.9.6.