🗓️ Release date:
This release of PocketQuery is a bug fix and security release.
Bug Fixes
-
Queries run from another query's template now keep their REST pagination and parameter settings.
Security
-
Values of a REST datasource's headers and request parameters are now removed from query results.
-
Keys and passwords in a REST datasource's URLs are now removed from query results.
-
REST datasource credentials echoed in less common encodings are now removed from query results as well.
-
SQL functions that run SQL text passed to them as a string are no longer permitted.
-
The @macro.id wildcard is now set by PocketQuery and can no longer be changed by page viewers.
Compatibility notes
-
REST headers and request parameters: Every value of a REST datasource's request headers and request parameters now counts as a credential, unless its name is a known setting (such as
Accept,Content-Type,limit,pageorNotion-Version) or the value is shorter than four characters,trueorfalse. Where a response contains such a value, the result shows[redacted]instead, or is not shown if PocketQuery cannot remove it. -
REST datasource URLs: Values in the query string and the user name and password in a REST datasource's URLs are treated the same way.
-
SQL queries: Queries that use the following functions are no longer run — on PostgreSQL
ts_stat,ts_rewrite,query_to_xmlschema,cursor_to_xml,cursor_to_xmlschema,crosstab,connectby,xpath_table,pg_background_launch,query_export_to_s3and the functions of thecron,aws_s3andaws_lambdaextensions; on OracleDBMS_XMLQUERY,DBMS_XMLSTORE,DBMS_XMLSAVE,DBMS_HS_PASSTHROUGHandDBMS_CLOUD; on SnowflakeTO_QUERY; on Db2XMLQUERY,XMLTABLEandXMLEXISTS. On PostgreSQL, a column qualified with a table name that is also the name of a function PocketQuery does not permit (such ast.sleep) is refused too. -
@macro.id: The wildcard always holds the ID of the PocketQuery macro on the page. In the query preview and in Rovo, where there is no macro, it is empty.
Internal version number: 2026-11-10