MySQL for Visual Studio 2.0.3 m2 release has been released

Dear MySQL users,

MySQL for Visual Studio 2.0.3 M2 is the second 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/doc/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.

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

MySQL for Visual Studio can also be downloaded by using the product
standalone installer found at
http://dev.mysql.com/downloads/windows/visualstudio/.

Changes in MySQL for Visual Studio 2.0.3 (2016-07-01, Milestone 2)

    Known limitation of this release: Some features such as Entity
    Framework and some Server Explorer functionality like drag & drop
    elements into a Dataset Designer or Design Tables do not work in this
    version.

      * Functionality Added or Changed

      * Bugs Fixed

    Functionality Added or Changed

      * Improved the handling of errors to manage exceptions from
        MySQL Shell, and to display relevant information about the
        exceptions in the selected output. This includes the full error
        message from MySQL Shell.

      * Added SSL support for MySQL connections that use the X
        Protocol. SSL support works with PEM files, so SSL connections
        need to be created through the "MySQL Connections Manager" in
        MySQL for Visual Studio, or from MySQL Workbench.

      * Added support for the following X DevAPI functions:
        parseUri() and isOpen().

      * A new MySQL Output pane was added that contains a results
        grid view similar to the view found in MySQL Workbench.  It
        contains the following data for executed statements: Success,
        Execution index, Execution Time, Query Text, Message (output from
        the server), and Duration / Fetch.  This functionality is
        available for JavaScript and Python queries.

      * Added "Console Mode" support for JavaScript and Python
        script editors, where query execution mimics the way the MySQL
        Shell works, meaning X DevAPI statements are executed after
        hitting "ENTER" and results are displayed inline.

      * Added the ability to switch between "Batch" (execute
        multiple statements) and "Console" (execute each statement after
        pressing Enter) modes, from the Query Editor toolbar as a
        dropdown list.

      * A MySQL connection manager dialog was added to help fully
        manage MySQL connections. It supports connection sharing with
        MySQL Workbench, and supports create, edit, configure, and delete
        actions.  MySQL connections created with the connection manager
        where the password is securely stored in the system's password
        vault functions with the Server Explorer in Visual Studio. The
        password is extracted from the password vault, and persists in
        the Server Explorer connections.

    Bugs Fixed

      * The "mysqlx" module was not imported properly to execute
        JavaScript queries. (Bug #23091964, Bug #81052)

      * After opening a valid MySQL connection and creating a new
        JavaScript MySQL script, disconnecting then reconnecting to the
        MySQL Server while changing the port to 33060 would fail.

      * MySQL for Visual Studio now shows a message stating that
        a SSL connection is required by the MySQL server if the
        require_secure_transport variable is set.

      * All script editors now display detailed information about
        the connection used. Before, the information was displayed in the
        toolbar as labels, but now all information is consolidated in a
        menu opened where the connection name is displayed. Additional
        information includes the connection method, host identifier,
        server version, user, and schema.

      * Output from executing JavaScript and Python commands were
        not visible unless the Output window was already opened.  The
        Output window now automatically opens when executing commands.


On behalf of the Oracle MySQL Release Engineering Team,
Nawaz


-- 
MySQL Announce Mailing List
For list archives: http://lists.mysql.com/announce
To unsubscribe:    http://lists.mysql.com/announce