Oracle .NET MySQL 8.0.21 Client throwing strange "same name are not supported" error

1

When I upgraded from MySQL Client 8.0.20 to 8.0.21 in a .net-core 3.1 application, I get this strange error when trying to call a stored procedure in AWS Aurora.

MySql.Data.MySqlClient.MySqlException (0x80004005): same name are not supported.
   at MySql.Data.MySqlClient.ProcedureCache.GetProcData(MySqlConnection connection, String spName)
   at MySql.Data.MySqlClient.ProcedureCache.AddNew(MySqlConnection connection, String spName)
   at MySql.Data.MySqlClient.ProcedureCache.GetProcedure(MySqlConnection conn, String spName, String cacheKey)
   at MySql.Data.MySqlClient.StoredProcedure.CheckParameters(String spName)
   at MySql.Data.MySqlClient.StoredProcedure.Resolve(Boolean preparing)
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)

In 8.0.20 (and several previous versions), it worked without any complaint. I can find nothing on the InterTubes about this error.

Procedure (very simple search proc):

CREATE DEFINER=`cdapoe`@`%` PROCEDURE `find_oeauthorizationassigned`(
IN p_username VARCHAR(120),
IN p_active_utc DATETIME
)
    READS SQL DATA
select * from oeauthorization.oeauthorizationassigned
where username=p_username and (p_active_utc < expiration_utc or expiration_utc is null)
mysql
.net-core
asked on Stack Overflow Sep 10, 2020 by Robin Johnson • edited Sep 11, 2020 by Robin Johnson

1 Answer

1

Downgrading from MySQL Client 8.0.21 to 8.0.20 is a known-good workaround.

The bug has been reported to and acknowledged by Oracle.

answered on Stack Overflow Sep 28, 2020 by David LapeŇ°

User contributions licensed under CC BY-SA 3.0