Bug #26344 MySqlDbType.Datetime should be MySqlDbType.DateTime
Submitted: 13 Feb 2007 21:12 Modified: 13 Nov 2007 11:45
Reporter: Karl Seguin Email Updates:
Status: Closed Impact on me:
Category:Connector / NET Severity:S4 (Feature request)
Version:5.X OS:Any
Assigned to: CPU Architecture:Any
Tags: .net, connector, naming

[13 Feb 2007 21:12] Karl Seguin
To be consistent with the .NET framework DateTime class, as well as the SqlClient's DateTime type, it would be nice if the MySQL type would be cased the same (capital 'D' and 'T').

The entire library should follow Microsoft .NET design guidelines.

How to repeat:

Suggested fix:
It might be too late to make this change, but .NET allows multiple enums to have the same underlying value, so this *could* be introduced without breaking existing code. However, it might confuse users as to which they should use (even though they are both the same).
[5 Nov 2007 22:31] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[5 Nov 2007 22:32] Reggie Burnett
Fixed in 5.1.4
[13 Nov 2007 11:45] MC Brown
A note has been added to the 5.1.4 changelog: 

The MySqlDbType.Datetime has been replaced with MySqlDbType.DateTime. The old format has been obsoleted
[20 Nov 2008 18:24] Jimmy Kim
Connector 5.2.4 or 5.2.5 -- the vs2008 designer keeps inserting Datetime rather than DateTime and thus this warning...

warning CS0618: 'MySql.Data.MySqlClient.MySqlDbType.Datetime' is obsolete: 'The Datetime enum value is obsolete.  Please use DateTime.'

Is this a problem on my machine?  I've had previous versions installed and uninstalled. -- My previous version was 5.1.2