Page tree
Skip to end of metadata
Go to start of metadata

Highlight of the release

  • Queries can now use the same renderers as Spreadsheets,
  • Rich / Static / Print layouts,
  • Resizable columns,
  • User Parameters for queries,
  • Upgrade of the system requirements,
  • MySQL and Oracle users are still unsupported, but they have a specific dialect.

There are so many changes and improvements in this release that we hope to satisfy many user requests in one single version.

Goodies

Customers with massive spreadsheets will particularly appreciate this one:

Autofilters !

When you need to select a few rows among hundreds, click the header
and start typing. Dates, numbers, text, those instant filters will help you a lot.

Tip: If you have several criteria, they use OR by default. You can
articulate your conditions with AND, OR and parenthesis for custom
matchers.

Pagination

 

Queries can now use the same renderers as Spreadsheets

This is a major rework. In queries:

  • Numbers can be formatted as currencies,
  • Text can be replaced with icons,
  • Markdown and links can be written.

Rich, Poor, Text and Print modes

Queries can now be inserted in several modes:

  • Rich: Red cell, sorting, filtering, copy/pasting, formatting and adding totals. The data is fetched dynamically, after the page is displayed.
  • Poor: Displays the result as a pure Confluence table, without the dynamic features,
  • Print: This is the default mode for PDF and print. It is equal to Poor. The data is fetched within the original page.
  • Text: You can use a result "inline" in a text. Play SQL adds invisible HTML mark-up, should you want to apply your own CSS.

User Parameters for queries

This is often requested so Queries can now display a form above the table where the users can update the query parameters.

In the Query Editor, use variables:

In the page, prompt for those variables:
 

Important notice: Upgrade task and new system requirements

  • PostgreSQL users have no action to perform. Users of Oracle and MySQL must update their database dialect from Generic to Oracle or MySQL. Those dialects are still not supported, but we provide a "best effort" mode to keep displaying their queries. See  PLAYSQL-87 - Getting issue details... STATUS
  • Confluence 5.3 or superior is required: This version of Confluence was published 1 year ago; The latest is 5.6.3. Play SQL requires the important user management and visual improvements of Confluence 5.3. 75% of our customers use a recent version of Confluence, and we have noticed that the minority of customers with an older version don't tend to upgrade the plugin anyway. If this requirement impedes your work, please contact us and we'll work with you to backport bugfixes.
  • Java 7 or superior: Java 6 is end-of-life by Oracle since Feb 2013 and isn't supported by Atlassian since then.
  • Better header compliancy. Play SQL used HTTP headers such as "COL-NAMES". Even if RFC-6648 (June 2012) has standardized that all headers should be accepted, some routers keep munching those which don't start with "X-". Therefore all Play SQL HTTP headers have been prefixed with X-, such as "X-COL-NAMES".

Issue list

Key Summary T Status Resolution Component/s
Loading...
Refresh

Upgrade notes

(warning) If you upgrade from Play SQL 1.4.1, please upgrade to 2.3.x first, otherwise your queries will be lost.

If you've upgraded too soon, please reinstall Play SQL 2.3.x, then upgrade to the latest version.

Known issues

Key Summary T Status Resolution
Loading...
Refresh

 

  • No labels