Changelog

Changed

• Added support for MySQL 5.7.
• Added a filter option to connections to filter schemas and databases in the explorer.

Changed

• Relationships: Browse foreign key relationships in data to view related data in other tables.
• Edit data and access relationships for your select queries.
• Aiven cloud provider added.

Fixed

• PostgreSQL showed duplicate columns in the foreign key when a foreign key had multiple columns.
• SQLite did not show columns in the explorer whose names matched the table name.

Fixed

• Codelens now indicates whether you are executing a selection or the entire document.
• libSQL now supports encrypted local files.

Changed

• Cloud providers support added. (more details)

Changed

• Added libSQL support (local file and Turso URL).

Fixed

• Changes to an open connection that affect the connection (e.g., host, port, username, etc) will now prompt you to close and reopen the connection.
• Color changes will be removed when the window loses focus and reapplied when the window regains focus to prevent them from appearing in other VS Code windows.

Changed

• Assign a color to a connection and specify which sections: the editor tab, status bar, and command center should display that color when active.

Fixed

• Codelens does not get hidden above the visible area.
• A race condition restoring previously open connections caused multiple connections to the same database to open.

Changed

• Open a table cells content in the VS Code editor.
• Connection tree view items are now cached for faster initial loading and refreshed in the background.
• The connection tree view will reopen previously expanded items on VS Code restart.
• Files assigned to a connection are now restored to that connection upon reopening VS Code.

Fixed

• Consistency with delete confirmations between connections, tunnels, history.

Fixed

• Fixed domain authentication bug in SQL Server, new option to be specific about authentication type added to connection.
• Fixed PostgreSQL not using right port when first adding a connection.

Changed

• Added an option to import from a connection string when adding or editing connections.
• Added zero-config functionality to automatically detect connections in .env and web.config files. (more details)
• Added compass (discovered) icons to the tunnels and connections that are automatically discovered.

Fixed

• Fixed an issue where SQLite connections would not store the file path when edited in some cases.
• PostgreSQL is the default connection type when adding a new connection.

Fixed

• Updated Microsoft Authentication to use common tenant.

Changed

• Added license information, customer portal and license purchasing to Account view.

Changed

• Added option to securely share reports.
• Added an Account view to enable authentication via VSCode authentication providers, necessary for secure report sharing.
• Added image preview when hovering over image in binary field.

Fixed

• Mongo protocol was not correctly saved when editing a connection.
• Editing connections in groups would cause them to ungroup.

Changed

• Binary fields containing images now display thumbnails in the results.
• String fields exceeding 500 characters are trimmed, displaying the total size at the end.
• Tooltips added for all result columns with values longer than 200 characters/bytes.
• Options to export all results, a selection, or selected rows.
• Export results in various formats: CSV, Excel, SQL insert statements, JSON, XML, Markdown, or HTML.
• Copy a selection or selected rows as text, CSV, SQL insert statements, SQL In Clause, JSON, XML, Markdown, or HTML.
• Added the ability to duplicate rows when editing results.
• Context menu includes options to add, duplicate, and delete rows if the results are editable.

Fixed

• Marketplace listing colors.
• Number rounding on tab badges.

Changed

• SQLite support added.
• Added option to explore with a sample database.

Fixed

• The results table now better aligns with the VS Code theme.
• Fixed an issue where editing stored procedures incorrectly indicated an error had occurred.
• MySQL did not correctly handle integers bigger than the javascript limit.