未加星标

MySQL for Visual Studio 2.0.4 has been released

字体大小 | |
[数据库(mysql) 所属分类 数据库(mysql) | 发布者 店小二03 | 时间 2016 | 作者 红领巾 ] 0人收藏点击收藏

The mysql windows Experience Team is proud to announce the release of MySQL for Visual Studio 2.0.4 m3 . Note that this is a development previewrelease and not intended for production usage.

MySQL for Visual Studio 2.0.4 m3 is the thirddevelopment preview release of the MySQL for Visual Studio 2.0 series. This series adds support for the new X DevAPI. The X DevAPI enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/ . For more information about how the X DevAPI is implemented in MySQL for Visual Studio, and its usage, see http://dev.mysql.com/doc/refman/5.7/en/mysql-shell-visual-studio.html .

Please note that the X DevAPI requires at least MySQL Server version5.7.12 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/5.7/en/document-store.html .

You can download MySQL Installer from our official Downloads page at http://dev.mysql.com/downloads/installer/ .

MySQL for Visual Studio 2.0.4 m3 can also be downloaded by using the product standalone installer found at http://dev.mysql.com/downloads/windows/visualstudio/ , under the tab “Development Releases”.

Changes in MySQL for Visual Studio 2.0.4 m3 What’s new in 2.0.4 m3 Enhanced the logic that migrates stored MySQL connections to the MySQL Workbench connections.xml file. In previous versions, the migration was offered and if not done at that moment, the dialog to migrate was shown every time the MySQL Connections Manager dialog was shown, but there was no way to choose to remain storing MySQL connections in the MySQL for Visual Studio configuration folder instead of merging them with MySQL Workbench. Now, the connection migration dialog offers a way to postpone the migration by either 1 hour, 1 day, 1 week, 1 month or indefinitely. If the migration is postponed, the dialog is shown again after that time elapses. If it is postponed indefinitely, then an option is added to the MySQL Connections Manager dialog that permits the connection migration to be done manually, as long as MySQL Workbench is installed. When the MySQL Script Editor window is opened (either by selecting SQL, javascript, or python from the New MySQL Script menu), the Results area was visible showing a big gray area in the editor, despite having nothing to display. Now, this area is hidden until results are ready to display, which happens after clicking Run. The SQL syntax parser was updated to handle the optimizer hints that were introduced in MySQL 5.7.7. The SQL editor was updated to check the syntax of a script before sending the statements to the server. If syntax errors are present, the Visual Studio Output pane displays the errors and the script is not executed. A drop-down list of connections was added in the MySQL editor toolbar to enable fast switching among connections while editing SQL, JavaScript, and Python scripts. The list, located next to the Connect to MySQL button, shows all Server Explorer connections for the MySQL data provider with compatible protocol support. Note JavaScript and Python editors show only the connections that support the X Protocol. Bugs Fixed MySQL Workbench was unable to open connections added fromthe MySQL Connection Manager, as executing them would emit thefollowing error: “Cannot connect to Database Server”. This isbecause an invalid “socket=.” value was added to the connectiondefinition. To solve this, MySQL for Visual Studio was updated touse the latest MySQL.Utility version, which fixes code in theMySQL Workbench class to only write the socket value into the XMLnodes if the connection is of type Sockets or Pipe. Bug#24666952 After connections were added to the Server Explorer through the MySQL Connections Manager, clicking Refresh on the Server Explorer toolbar caused the refresh operation to hang, and nothing else could be done within the Server Explorer pane. Clicking Cancel Refresh was required to fix this. Bug #24666931 SHOW statements executed from the SQL editor failed todisplay the expected output. Bug #24622881 Queries executed from the SQL editor against nonunique data in NoSQL tables emitted error messages and failed to returnresult sets. Bug #24462707 The main XML element in %APPDATA%\Oracle\MySQL For VisualStudio\settings.config was renamed to MySQLforVisualStudio fromMySQLForExcel. Indentations were added to improve the overallreadability of configuration settings. Bug #24291264 JavaScript and Python editors permitted connections toversions of MySQL that did not support the X Protocol if thoseconnections were unnamed or temporary, but the scripts did notwork properly. This fix adds validation to ensure that allconnections related to JavaScript and Python scripts are toservers with the X Plugin enabled. Bug #24290570 Selecting the New MySQL Script context-menu option byright-clicking a Server Explorer connection in Visual Studioemitted an error if the connection was first closed and then opened. Bug #24064816 Visual Studio was unable to open a design window for anyselected table in a MySQL database. Bug #23642010 Opening a new MySQL script file from the Visual StudioFile > New menu displayed the following error: “Object referencenot set to an instance of an object”. Bug #23619311 Processing a Result object from the X Protocolsubstituted an error or information message in place of somecollection output. Bug #22983803 Advanced, Connect, and Cancel buttons were missing fromthe Connect to MySQL dialog for connections made from the scripteditor window. Bug #22114315 Dragging and dropping a table from the Server Explorer inVisual Studio to a project would fail with the following error:“Some updating commands could not be generated automatically. Thedatabase returned the following error: You have a usableconnection already”. After clicking OK, Visual Studio would emitthe following error “Mouse drag operation failed. Could notretrieve schema information from table or view”. To solve thisissue, MySql.Data was updated to version 6.9.9. From the Query Designer, selecting Verify SQL Syntaxwould always display “Not supported by the provider” instead ofverifying the SQL syntax. The Python code editor displayed session options forJavaScript instead of options for the Python language. In some cases, selecting Retrieve Data for a table with avalid connection failed to populate the table with data. Quick links MySQL for Visual Studio documentation

本文数据库(mysql)相关术语:navicat for mysql mysql workbench mysql数据库 mysql 存储过程 mysql安装图解 mysql教程 mysql 管理工具

分页:12
转载请注明
本文标题:MySQL for Visual Studio 2.0.4 has been released
本站链接:http://www.codesec.net/view/480721.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 数据库(mysql) | 评论(0) | 阅读(33)