MySQL Forums
Forum List  »  Announcements

MySQL for Visual Studio 2.0.2 m1 Development Release has been released
Posted by: Karen Langford
Date: April 11, 2016 02:39PM

Dear MySQL users,

MySQL for Visual Studio 2.0.2 M1 is the first development 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/docs/refman-5.7/en/mysql-shell-visual-studio.html.

Please note that the X DevAPI requires at least MySQL Server version
5.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.

Changes in MySQL for Visual Studio 2.0.2 (2016-04-11, Milestone 1)

   Known limitation of this release: SSL connections are not yet
   supported.

   Functionality Added

     * Added support for Visual Studio 2015 with .NET Framework
       4.6.

     * Added support for Python scripts. Python code can now be
       executed and can interact with the X DevAPI introduced in
       MySQL 5.7.12, where relational and document data can be
       queried. Extended views (Field Types, Query Statistics and
       Execution Plan) are not available for Python in this version.

     * Added new result views for document-based (JSON) data
       returned by MySQL X, where data can be viewed in a grid,
       tree, or text representation.

     * Added a new Javascript query type, in addition to SQL
       type that was already present. JavaScript code can be
       executed and interact with the X DevAPI introduced in
       MySQL 5.7.12, where relational and document data can be
       queried. Extended views (Field Types, Query Statistics
       and Execution Plan) are not available for JavaScript in
       this version.

     * Enhanced the user interface for query scripts where
       different views for result sets returned by the MySQL
       Server are now available, similar to the ones in MySQL
       Workbench. For SQL scripts the available views are:

          + Results: shows returned data

          + Field Types: shows information about columns of a
            result set, such as names, data types, character
            sets, and more.

          + Query Statistics: shows information about the
            executed query, such as execution times, processed
            rows, index and temporary tables usage, and more.

          + Execution Plan: shows a text-view explanation of the
            query execution performed internally by the MySQL
            Server.

     * After MySQL scripts are executed, each result set
       returned by the MySQL Server is now displayed in a
       separate Results tab. In previous versions, only the last
       result set returned by MySQL Server was displayed in the
       Output tab.

     * Added an option to create MySQL scripts directly from a
       MySQL Server instance in the Server Explorer. This
       simplifies the process of creating scripts, as there is
       no longer a requirement to open a connection for each
       script like in previous versions of MySQL for Visual
       Studio.

   Bugs Fixed

     * Fixed the coloring of SQL code so it is readable on any
       VS color theme, like the "Dark" one.


On behalf of the MySQL Release Team 

Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL for Visual Studio 2.0.2 m1 Development Release has been released
2145
April 11, 2016 02:39PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.