-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose MySqlDbType #362
Comments
Would it be enough to rename Or do the internal types have to match the MySql.Data types: public enum MySqlDbType
{
Decimal,
Byte,
Int16,
Int24 = 9,
Int32 = 3,
Int64 = 8,
Float = 4,
Double,
Timestamp = 7,
Date = 10,
Time,
DateTime,
[Obsolete("The Datetime enum value is obsolete. Please use DateTime.")]
Datetime = 12,
Year,
Newdate,
VarString,
Bit,
JSON = 245,
NewDecimal,
Enum,
Set,
TinyBlob,
MediumBlob,
LongBlob,
Blob,
VarChar,
String,
Geometry,
UByte = 501,
UInt16,
UInt24 = 509,
UInt32 = 503,
UInt64 = 508,
Binary = 600,
VarBinary,
TinyText = 749,
MediumText,
LongText,
Text,
Guid = 800
} |
A lot of the values will probably overlap (because MySql.Data may conflate the two enums). |
Yes I noticed MySqlDbType is missing column types like int and char. They are valid types however, that's why they need to be in GetSchema() |
Implemented in 0.29.0. |
The integer values of
MySqlDbType
are exposed by Connector/NET inGetSchemaTable
(#307) andGetSchema
(#361).MySqlParameter
also has aMySqlDbType
property.Clients may be relying on the presence of this type in the public API and on its exact values.
The text was updated successfully, but these errors were encountered: