Bug #62939 Entity framework stored procedure mapping fails
Submitted: 26 Oct 2011 3:26 Modified: 15 Nov 2011 12:41
Reporter: Leroy Casterline Email Updates:
Status: Closed Impact on me:
Category:Connector / NET Severity:S1 (Critical)
Version:6.4.4 OS:Windows (Win-7 x64 Ultimate)
Assigned to: Bogdan Degtyariov CPU Architecture:Any
Tags: entity framework, stored procedure mapping

[26 Oct 2011 3:26] Leroy Casterline
Stored procedure mapping fails to identify the procedure’s parameters.

NOTE: I set the severity to critical because it is the only defined choice when there is no workaround. 

MySQL Version: 5.1.56
VS2010 SP1
Connector version: 6.4.4

How to repeat:
1.Have a sample database with stored procedures to:
  a. Insert a row into a table
  b. Update a row in the same table
  c. Delete a row from the same table
2.In VS2010, create a new class library project
3.Add a new ADO.NET Entity Data Model to the library
4.Elect to generate the model from the sample database
5.Create the model using default parameters
6.Open the model
7.Right-click on the entity with the stored procedures and select ‘Stored Procedure Mapping’
8.On the mapping pane, select your Insert, Update and Delete stored procedures
9.Observe that no parameters are identified for the Insert and Update procedures

Suggested fix:
The stored procedure parameters should be identified and displayed on the mapping pane.
[15 Nov 2011 12:37] Bogdan Degtyariov
Hi Leroy,

Unfortunately, the stored procedure parameter mapping is not working with MySQL Server 5.1. Only MySQL Server 5.5 provides the necessary parameter metadata (PARAMETERS table in Information_Schema database exists only in version 5.5).

You can also check the screenshot (vs2010_sp_param_mapping.jpg) which demonstrates the correct parameter mapping in Visual Studio 2010 with MySQL 5.5 and Connector/NET 6.4.4.

So, please use MySQL 5.5 if you really need the parameter mapping working.
[15 Nov 2011 12:40] Bogdan Degtyariov
SP parameter mapping in VS2010

Attachment: vs2010_sp_param_mapping.jpg (image/jpeg, text), 285.53 KiB.

[15 Nov 2011 12:41] Bogdan Degtyariov
The parameter mapping is not going to be supported for MySQL 5.1.
Closing the bug.