A new maintenance release of SOQL Studio is now available for download. Version 2018.2.270 includes several enhancements and minor bug fixes. In this post I’ll provide a complete list of the changes as a well as go into detail on some of the more significant changes.
- Added query run-time statistics as Informational messages
- Improved handling of “duplicate” SOQL Editor tabs
- Added support for API version 44 (Winter ’19)
- Enabled copying of selected rows in the Messages tool window
- Improved handling of authentication failures throughout the application
- Implemented a work-around to an API quirk that caused SOQL errors returned from Salesforce to exclude row/col information
- Fixed an issue that caused an Index out of range exception to be thrown when generating a browse query from the Organizations tool window
- Corrected an issue introduced in the last maintenance release that could cause the application to crash when right-clicking in the results grid
- Corrected an issue that could cause the application to crash when processing the results from a query that included a child rows from a recursive relationship
- Fixed an issue that, under certain circumstances, caused the “View in Salesforce” and “Edit in Salesforce” context menu items to either not be shown when clicking on an ID field or shown when clicking on a non-Id field
Run Time Statistics
Run time query statistics is a feature that comes courtesy of Visual Database Explorer, our ODBC-based SQL query product, and is something we’ve had on our enhancement list since day 1. We implemented this as a set of Informational messages presented in the Messages tool window. Like any other editor-scoped message, each SOQL Editor gets its own set of statistics when a query is executed. Re-executing a query clears the existing statistics and generates new ones. The messages provide a timestamp of when the query was executed, what Org it ran on, the amount of time it took to execute and the amount of time it took to render the results.
In prior versions of SOQL Studio, you could open the same SOQL file in multiple tabs, make changes to each, and save them. What you were left with in the file on disk was the contents of the SOQL Editor that was last saved. This may or may not be what you wanted. We enhanced the SOQL Editor to detect when the file being opened is already open in another editor tab and to visually label it with a “(n)”, where n is a number to make the name unique. For example, if you have c:\users\public\documents\Accounts.soql open it will appear as “Accounts.soql” in the editor. If you open that same file again while Accounts.soql is open, the second tab will show as “Accounts (1).soql”. When you save your changes to Accounts (1), it will bring up the Save As dialog to allow you the opportunity to rename the file. This small change helps ensure that you don’t inadvertently overlay a .soql file you wanted to keep.