Highlight of the release
- Full-screen mode and more features to work with many rows,
- Permissions at a space level
- Excel export
- Removal of the Legacy SQL macro
As data grows bigger, sometimes we need to squeeze more rows and columns on the screen. We're adding a few widgets to make this simpler.
New options for column resizing
New options for viewing large amounts of data
It is difficult to explain the feeling of the distraction-free mode. The browser collapses and displays the table in full-screen mode, like a Youtube video. Margins can also be reduced.
These options are displayed when the pagination is active (more than 50 records). In full-screen mode, inline dialogs aren't available, so it is not possible to edit the column properties or have autocomplete on formulas. Those options are available in reduced-margins mode.
We're introducing space permission overrides for advanced permission tuning:
- By default in Play SQL, there are permissions for:
- View: Viewing all data, filtering and sorting,
- Edit: Edit rows, add rows,
- Structure: Edit columns, change types,
- Admin: Change the datasource properties.
- The space permissions apply: Only users who can view the space can view spreadsheets, etc.
- It is possible to enlarge the audience: "Accepted Groups" are groups which are accepted in addition to the space users. If the "Inherit from space" checkbox is unticked, only the accepted groups will be allowed.
- It is possible to restrict the audience: For example administrators could decide that only Board Members can see the data. The group "Board Members" will be added to Required Groups.
- It is possible to specify a database password for each level.
Clients who have configured Play SQL with a JNDI datasource are the best. However, it is only possible to override the database password for each permission if you use a JNDI provider which allows overriding the password. Our previous example of JNDI datasource used Tomcat's DBCP, which doesn't support this feature. We've updated our example to use C3P0. See Declaring a JNDI datasource for Confluence.
We're introducing an export into Excel. It has limited features:
- Several spreadsheets can be exported as several tabs in an Excel workbook,
- Data and columns only are exported,
- Formulas, audit trail, settings aren't exported. The feature is provided as one way to manage the data in Excel, but a full SQL access allows full access to all your data in read-write mode and in clear text.
Note that exporting a full table can draw the server's resources and exporting a full space can be more difficult, depending on the amount of exported data. Therefore this feature is only available for administrators. There are options for system administrators to change the default timeout (60s) or disable the feature. See - PLAYSQL-174Getting issue details... STATUS for more information.
Removal of the Legacy SQL macro
Here is what the Legacy SQL Macro used to look like:
The legacy macro is deprecated since October 2013. We're proceeding to removing the Legacy SQL Macro in 2 steps:
- Play SQL 2.11 We don't display the macro anymore in the autocomplete and we only allow sysadmins to use it. Existing macros will still work.
- Play SQL 2.12 We'll completely remove the macro and the code.
The reason for removal is it requires maintaining a swarm of dedicated code. Too much code is bad because:
- Legacy code pulls productivity down, so fewer features are developed for the other customers.
- Legacy code augments exposure to risk. Every API needs to be regularly tested for permissions, and the deprecated APIs are using the old permission scheme.
Besides, all features were moved to the modern "Query" and "Spreadsheet" macros.
Workarounds and mitigation:
- Replace the legacy macro with the normal Query macro,
- If there is a problem with dropping this feature, avoid upgrading to the latest version and tell us what is holding you back.
- Errors will be displayed in the logs when the deprecated features are being used and the identity of the user. This logging can be turned off using the system property -Dplaysql.mute-deprecation-warnings.
- As explained above, the Legacy SQL Macro is removed. Please do not upgrade if you still require it.
- If you upgrade from Play SQL 2.6, there are new requirements:
- Requires Java 7,
- Requires PostgreSQL 9.2,
- Requires Confluence 5.3,
- From November 2015, requires IE10 (see Atlassian Confluence's end of support announcement for IE9).
- If you upgrade from Play SQL 2.9, there are schema changes:
- You may wish to back-up your database before upgrading.
- See Release Notes 2.10 - Upgrade Guide for more information,