( Note: this is a news article about the new PocketQuery version 2.1. If you’re searching for the documentation, find it here).
PocketQuery 2.1 says hello to the world! In this release, we focused primarily on one desire we’ve heard from many PocketQuery users: decouple the PocketQuery Administration from the Confluence Administration! But there are also a few other new minor features that might come handy for you!
Group-based PocketQuery administration
It has been a limitation in the past that only Confluence administrators could access the PocketQuery administration. We tackled this limitation with version 2.1. Additionally to Confluence administrators, a group of PocketQuery administrators can be defined in a new PocketQuery configuration screen.
All users who are able to administer PocketQuery, will have a new link to the PocketQuery administration screen in their user menu in the top right:
The old “Pocket Queries” menu link in the Confluence administration will stay alive for some time, but is now clearly stamped deprecated.
Query parameters of type Boolean
Previously, if you had a boolean value as a query parameter, the value was always translated to a string before it was executed. You can now use a parameter type Boolean for this purpose. Example:
Query parameters in SELECT clauses
Using the new parameter type Constant you can now have query parameters in the select clause.
SELECT Name, Population, :AdditionalColumn FROM Country WHERE Continent = :Continent
Render custom templates also when errors occured
Previously, custom templates were only rendered if no errors occurred in the PocketQuery execution. But you might also display something specific if there was an error. Now you can do this in your template:
#if (!$result) There was an error with the query. #else ... #end
Deactivate auto-load for dynamic load
There is now a new macro parameter checkbox “Disable autoload” when the “Load macro dynamically” and “Use change params template” options are checked. If this is checked, the PocketQuery macro won’t be loaded upon page load, but only when the “Change” button in the form is clicked.
- Double colons are not interpreted as parameters anymore. Some PostgreSQL statements use double colons as meta-syntax which caused problems earlier.
- Column order was sometimes changed as soon as the caching option was checked on a query.
- Special characters & and = could previously not be used in query parameters.