I am continuing to develop the tool further as my understanding of advanced queries improves.
One key area that took me some time to appreciate is that there are two types of major retrieval mechanisms and I am implementing them for v0.2 of the onlline tool which I should release in the next week or two
Type 1 retrieval is for each page (which has a ‘special block’ of its own which I detect by presence of :block/original-name. All the page attributes are available in the query results ie page tags, page properties, alias, original page name(case sensitive) and pagename (lower case) and are returned in the query result.
Type 2 is for every block in the graph (which includes the page special blocks) and it has references to the page that owns the block. However it returns only the block in the result.
Wish me luck
PS it would be great if the type 2 queries returned the page title in the result. Still haven;t worked out how to get that as a property in the result
clarify pages retrieval vs blocks retrieval in FAQ, Simple Commands
Added ‘and’ and ‘or’ keywords in arguments for a command, For example can now say
- or tagA
- property category, "fiction"
- and property category, "western"
Added a logseq test graph download button to help user test advanced queries
Force user to choose either pages or block retrieval, Default to block retrieval
improved error messaging
improved descriptions for the generated advanced query lines
(1) The introduction of and and or prefixes will enable more control over boolean logic while still keeping the command arguments relatively simple
(2) You can now download the full test graph without the need to use the buildlogseqtestgraph tool. however if you want to control the random content and number of pages, journals, tags etc then you should use the buildlogseqtestgraph and ‘roll your own’ test graph.
(3) The test graph when downloaded contains over 40 advanced query examples that execute within the test graph