MySQL Bugs: #55778: Stored procedure parameters are omitted during update of the entity data model

Bug #55778	Stored procedure parameters are omitted during update of the entity data model
Submitted:	5 Aug 2010 11:41	Modified:	1 Jun 2011 16:25
Reporter:	Kostya Khodykin	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	6.2.3	OS:	Windows
Assigned to:	Julio Casal	CPU Architecture:	Any
Tags:	entity framework function import parameters

Description:
If user creates Entity Data Model, using entity framework with MySql, and wants to import stored procedure to the model, this stored procedure is imported without parameters, regardless it has any or not.

How to repeat:
1. Create siple routine which accepts parameter in the schema.
e.g.
CREATE DEFINER=`schema_name`@`%` PROCEDURE `searchProducts`(in searchString varchar(2000))
BEGIN
...
END
2. Create Entity data model from th existing database in the visual studio.
3. Try to import just created stored procedure
4. Observe created stored procedure in the Model Browser window (in VS)

Actual result:
No parameters are defined for the imported stored procedure

Expected result:
The imported stored procedure should have "searchString" parameter

Are there any workaround for this bug? I have tried to call  base.ExecuteFunction with parameters manually as below but it gives "Input string was not in a correct format." exception. 

return base.ExecuteFunction<vw_result_type>("storedprocedure", new ObjectParameter[] { new ObjectParameter("first_int_param", first_int_param), new ObjectParameter("second_int_param", second_int_param) });

Issue still exists with Visual Studio 2010 and MySQL Connector/.Net 6.3.6.  Imported a MySQL stored procedure and none of the input parameters were picked up.

any update on this bug?  We are encountering it in version 6.3.6 as well.

Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release.

Fixed versions: 6.0.8, 6.1.6, 6.2.5, 6.3.7, 6.4.1+

If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

i am trying with version 6.3.7 having the same issue

I just performed the function import in VS 2010 with the released Connector/Net 6.3.7 following the specified reproduction steps. The parameter is correctly identified and displayed in Model Browser.

If you have some specific scenario where the issue still exist please add your reproduction steps and the script for your stored procedure.

Hi I still Observer the Issue on the following environment.

Windows 7 x64
VS 2010 Professional Edition (No SP1)
5.5.13 MySQL Community Server (GPL)
MySQL Connector Net 6.4.3

The Parameter List is still empty.

Can you please try with VS 2010 with SP1?

Even with VS 2010 sp1, the issue is seen.

Anything solution to solve this problem?

I just did this:
1. Created the specified searchProducts stored procedure, which includes a searchString parameter.
2. Created a new Entity Data Model that only included that stored procedure.
3. From model browser, right clicked searchProducts under myModel.Store->Stored Procedures.
4. Selected Add Function Import from the context menu.
5. Clicked OK in the Add Function Import dialog.
6. The new function import is created and appears in Model Browser with the searchString parameter.

Environment:
Windows 7 x64
VS 2010 with SP1
MySQL Community Server 5.5.15
MySQL Connector Net 6.4.3

Anything I'm missing?

For me, the connector 6.4.3, presents the error "Unknown table 'PARAMETERS' in information_schema" to create the Model.

Environment:
Windows 7 x86
VS 2010 ULTIMATE with SP1
MySQL Community Server 5.1 (available in Host)

This is still occurring on my setup when adding a stored procedure which doesn't return anything.

MySql connector 6.4.3
Windows 7 x86
Visual Studio 2010 SP1
Entity Framework 4.1

I am also having this problem with Visual Studio 2010 and MySql Connector v6.5.4

I upgraded my version of MySQL to 5.5.20 and it seemed to correct my entity framework problem.