Bug #64377 | DCR: DateTime 0000/00/00 00:00:00 should be Nullable<DateTime> not MinTime | ||
---|---|---|---|
Submitted: | 19 Feb 2012 10:46 | Modified: | 28 Mar 2012 20:57 |
Reporter: | asdf asdfd | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | Connector / NET | Severity: | S3 (Non-critical) |
Version: | 6.6.4 | OS: | Windows (Win2k8r2) |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | ConvertZeroDateTime, MysqlDateTime |
[19 Feb 2012 10:46]
asdf asdfd
[19 Feb 2012 10:57]
asdf asdfd
Additional information available at: http://wasntnate.com/2012/02/mysql-data-getting-past-datetime-00000000-000000/
[28 Feb 2012 20:57]
Gabriela Martinez Sanchez
Dates range differences between Mysql and the .net framework are clearly different. So for this case I would recommend you to use the GetMySqlDateTime instead of the GetValue method, this way will give you the accurate table value instead of having the limitation of the DateTime type of the .net framework. Please check it and let us know if this option works for you or if you have any other comments. (http://dev.mysql.com/doc/refman/5.0/es/connector-net-examples-mysqldatareader.html#connect...). Regards,
[29 Mar 2012 1:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".