Documentation Home
MySQL for Visual Studio Release Notes
Download these Release Notes
PDF (US Ltr) - 91.4Kb
PDF (A4) - 90.6Kb

MySQL for Visual Studio Release Notes  /  Changes in MySQL for Visual Studio 1.1  /  Changes in MySQL for Visual Studio 1.1.4 (2014-03-10, General Availability)

Changes in MySQL for Visual Studio 1.1.4 (2014-03-10, General Availability)

This is a maintenance release for the MySQL for Visual Studio 1.1 series, and it is suitable for production environments. It is compatible with Connector/Net 6.8.3 and later, and it supports MySQL Server versions 5.0 to 5.6.

Functionality Added or Changed

  • Introduced a new MySQL toolbar, which provides shortcuts to some of the main functionalities of MySQL for Visual Studio. See Enabling the MySQL Toolbar for details.

Bugs Fixed

  • The MySQL parser did not recognize the full string literal syntax of [_charset_name]'string' [COLLATE collation_name] as supported by the MySQL Server. This fix makes Connector/NET and MySQL for Visual Studio recognize the string literal syntax as specified in Character String Literal Character Set and Collation, in the MySQL Server manual. (Bug #18169145)

  • In Visual Studio, the stored procedure debugger did not evaluate the last_insert_id() function in a watch expression correctly. This fix also corrects similar issues for two other information functions that query the debug data table: row_count() and found_row(). (Bug #18111085)

  • A new model could not be created with Entity Framework 6 in Visual Studio 2013 when using MySQL for Visual Studio 1.1.3 and Connector/NET 6.8.3. (Bug #18105394, Bug #71427)

  • The MySQL parser could not parse an if statement when there were any spaces before the parenthesis for the arguments (for example, if (1,1, 1)). Besides if, the same issue occurred for a number of other functions like row_count, ifnull, mod, repeat, and so on, and this fix corrects the problem for all of them. (Bug #17981407)

  • When debugging a stored routine in Visual Studio with the debugger, long identifiers caused the error "data too long for column 'pvarname'" to be thrown. That was because the SQL script of the debugger did not support the same lengths for identifier names as the MySQL server does. This fix matches the debugger with the MySQL server on the maximum lengths supported for identifier names. (Bug #17568158, Bug #70159)