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
Is your feature request related to a problem? Please describe.
We need support for legacy MySQL Server 5.0 similar to the level the MySql.Data provides.
Specifically, we use the MySql.Data.MySqlClient.MySqlCommandBuilder.DeriveParameters method to obtain the schema of a stored procedure.
The MySqlConnector.MySqlCommandBuilder.DeriveParameters throws an exception for server versions less than 5.5.3 due to the absence of "information_schema.routines".
Describe the solution you'd like
As I see, some fallback code using "mysql.proc" already exists in the CachedProcedure.FillAsync method. Use this code to derive parameters instead of throwing an exception.
Describe alternatives you've considered
We'd like to avoid re-implementing procedure parameter parsing on our side.
The text was updated successfully, but these errors were encountered:
If you'd like to open a PR to add the support you need (with code that is entirely your original contribution and able to be licensed to this project), I'd be happy to review it.
Is your feature request related to a problem? Please describe.
We need support for legacy MySQL Server 5.0 similar to the level the MySql.Data provides.
Specifically, we use the MySql.Data.MySqlClient.MySqlCommandBuilder.DeriveParameters method to obtain the schema of a stored procedure.
The MySqlConnector.MySqlCommandBuilder.DeriveParameters throws an exception for server versions less than 5.5.3 due to the absence of "information_schema.routines".
Describe the solution you'd like
As I see, some fallback code using "mysql.proc" already exists in the CachedProcedure.FillAsync method. Use this code to derive parameters instead of throwing an exception.
Describe alternatives you've considered
We'd like to avoid re-implementing procedure parameter parsing on our side.
The text was updated successfully, but these errors were encountered: