sorgel
October 30, 2025, 8:51am
1
Sure, the DB version is not released yet, so my questions can only be a problem of the alpha versions. I’ve downloaded the DB version recently, and now I am not sure how permanent the changes are in regard to advanced queries:
It seems that using properties is no longer available in advanced queries. At least, I could not make the basic example work, which works in the stable version:
{:title [:h2 “Programming languages list”]
:query [:find (pull ?b [*])
:where
(property ?b :prop "value")]}
Also, I don’t see properties in block data with developer tools.
Am I missing something? Maybe now there is another way to build queries with properties? Or would it be better to use new tags instead?
The :view command also seems not to be working in new queries. But actually, I’ve never mastered it, so, again, it can be my skills issue. But I would like to check if it’s just me.
danzu
October 30, 2025, 11:24am
2
Hi @sorgel
The advanced query still works, but note that some schema changes were introduced.
They are documented in:
## Description
This page describes changes for existing Logseq features on the [database version](https://github.com/logseq/logseq/pull/9858). Some of these changes may change depending on user feedback.
## Overview
* [Changes for All Graphs](#changes-for-all-graphs)
* [DB Graph Changes](#db-graph-changes)
* [File Graph Changes](#file-graph-changes)
## Changes for All Graphs
The following changes affect both file and the new db graphs:
* To simplify editor `/` commands, [Commands](https://docs.logseq.com/#/page/commands) and [Advanced Commands](https://docs.logseq.com/#/page/advanced%20commands) are merged together under `/`.
* A good amount of the UI is rewritten to use [shadcn](https://github.com/shadcn-ui/ui). This means a more beautiful, consistent and powerful UI!
* The application performance is better - loading faster, handling larger graphs and large tables. See https://github.com/logseq/logseq/pull/11774 for latest details.
* On desktop, the graph cache directory `~/.logseq/graphs/` has moved to `~/logseq/graphs`. See [DB Graph Directories](#db-graph-directories) for how they are used for DB graphs.
* Plugins can be used from the web. For security reasons only [plugins configured with no "effect"](https://github.com/logseq/marketplace#how-to-submit-your-plugin) are usable. We will gradually open up effect plugins to certified/trustworthy plugins.
* On browser, multiple tabs can be opened and kept in sync, even when offline. Syncing between tabs _does not_ require a sync server.
* The visibility of left sidebar items are configurable. To configure, hover over the `Navigations` header and click on the filter icon to open a dropdown for toggling visibility of sidebar items.
This file has been truncated. show original
## Description
This page describes changes for existing Logseq features on the [database version](https://github.com/logseq/logseq/pull/9858). Some of these changes may change depending on user feedback.
## Overview
* [Changes for All Graphs](#changes-for-all-graphs)
* [DB Graph Changes](#db-graph-changes)
* [File Graph Changes](#file-graph-changes)
## Changes for All Graphs
The following changes affect both file and the new db graphs:
* To simplify editor `/` commands, [Commands](https://docs.logseq.com/#/page/commands) and [Advanced Commands](https://docs.logseq.com/#/page/advanced%20commands) are merged together under `/`.
* A good amount of the UI is rewritten to use [shadcn](https://github.com/shadcn-ui/ui). This means a more beautiful, consistent and powerful UI!
* The application performance is better - loading faster, handling larger graphs and large tables. See https://github.com/logseq/logseq/pull/11774 for latest details.
* On desktop, the graph cache directory `~/.logseq/graphs/` has moved to `~/logseq/graphs`. See [DB Graph Directories](#db-graph-directories) for how they are used for DB graphs.
* Plugins can be used from the web. For security reasons only [plugins configured with no "effect"](https://github.com/logseq/marketplace#how-to-submit-your-plugin) are usable. We will gradually open up effect plugins to certified/trustworthy plugins.
* On browser, multiple tabs can be opened and kept in sync, even when offline. Syncing between tabs _does not_ require a sync server.
* The visibility of left sidebar items are configurable. To configure, hover over the `Navigations` header and click on the filter icon to open a dropdown for toggling visibility of sidebar items.
This file has been truncated. show original
Example of Advanced Query:
```clojure
{:query [:find (pull ?b [*])
:where
[?b :user.property/Player-bEMnJKfg ?player]
(or [?player :block/name “player a”]
[?player :block/name “player c”]]
}
```
If you do not see the block data, go to Logseq Settings >> Advanced >> Enable Developer Mode
`:view works, but :result_transform needs a bit of work
1 Like
sorgel
October 30, 2025, 4:46pm
3
Thank you so much! I tried not to miss something obvious, but somehow managed to do this.
sorgel
October 30, 2025, 7:50pm
4
Maybe that will help someone in future: I can mess something, but it looks like the right way to access the property value is by :block/title, not :block/name.
So in my case this does work:
{:query [:find (pull ?b [*])
:where
[?b :user.property/test-c_eBb5ly ?a]
[?a :block/title “rrr”]
]}
And this does not:
{:query [:find (pull ?b [*])
:where
[?b :user.property/test-c_eBb5ly ?a]
[?a :block/name “rrr”]
]}
Also dev tools suggest using the title instead of the name