You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi !
Actually with DbParameter implémentations lik SqlParameter or SqliteParameter (and so on...) we have mulitples constructors available.
For instance, SqlClient assembly have such constructors :
But (in my case for instance) I have to prepare all my parameters and set the values after.
So I have to deal with the parameterless constructor, actually:
This code was working with the official MySQL provider, since the parameter constructor public MySqlParameter(string parameterName, MySqlDbType dbType); is available.
In MySqlConnector the MySqlDbType variable becomes... the value !
I think it would be great to have ... sort of equivalence or compatibility with the MySQL official connector, at least for objects constructor.
We talk here about MySqlParameter, but IMO, it applies to all public objects.
Why do that ?
To have a smooth and easy migration from official MySql connector to MySqlConnector :)
Make sense ?
Sebastien
The text was updated successfully, but these errors were encountered:
Hi !
Actually with
DbParameter
implémentations likSqlParameter
orSqliteParameter
(and so on...) we have mulitples constructors available.For instance,
SqlClient
assembly have such constructors :Two main reasons to implements more constuctors in MySqlParameter
Just because it's obvious :)
In
MySqlConnector
we only have:In most of the cases, it's enough :)
But (in my case for instance) I have to prepare all my parameters and set the values after.
So I have to deal with the parameterless constructor, actually:
Compatibility whith official MySQL connector
Actually all my code is written like this:
This code was working with the official MySQL provider, since the parameter constructor
public MySqlParameter(string parameterName, MySqlDbType dbType);
is available.In
MySqlConnector
theMySqlDbType
variable becomes... the value !I think it would be great to have ... sort of equivalence or compatibility with the MySQL official connector, at least for objects constructor.
We talk here about
MySqlParameter
, but IMO, it applies to all public objects.Why do that ?
To have a smooth and easy migration from official
MySql
connector toMySqlConnector
:)Make sense ?
Sebastien
The text was updated successfully, but these errors were encountered: