logseq / logseq/db-test

Querying properties with Nodes and Plain Text as values can't find the node values.

Open
#1,085 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

According to the database version documentation:
> Text: This is the recommended default as it allows for any text and behaves like a block. `This means that node references work here` and children blocks can be created under the block.

But, if you create a property with `Multiple values` and some of them are **Nodes** and some of them are **Plain Text**, querying that property only finds the values that are **Plain Text**. It doesn't find the values that are **Nodes** with `[[]]`.

### Reproduce the Bug

1. Create a `Property` with **Property type** set to `Text` and also have `Multiple values`.
2. Add it to a **Node** and populate it with `Multiple values` with some of them being **Nodes** and a some of them **Plain Text**.
3. Try to Query the values. Only the values that are **Plain Text** show up. The values that are **Nodes** with `[[]]` do not show in the Query results.

### Expected Behavior

According to the documentation both **Nodes** and **Plain Text** values should work.

### Screenshots

_No response_

### Desktop or Mobile Platform Information

AppImage version 2.0.1 Beta

### Additional Context

_No response_

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the AppImage 2.0.1 Beta using a Text property with multiple values, mixing node references and plain text. Inspect the query path and existing database tests, if available, for how each value type is indexed or matched; done means query results include both the plain-text and node values.

Written by the indexing model from the issue text.

Assessment

Domain
database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.