logseq / logseq/db-test

Incorrect filtering of properties

Open
#1,054 0 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?

I seem to have an issue where the databases don't correctly filter properties. For example, I have set a property called 'author'. When I try to filter a specific author only one name with that property will show up. If I filter the exact same property again all of a sudden all of the names with that property will show up. At the top of the database it will say 'Author is ...' twice to indicate that I filtered the same property twice. If I remove one of these filters, they both disappear. Not all the properties have this issue. The properties with a set number of options ,like status or priority for example don't have this problem.

### Reproduce the Bug

1. Go to a tag.
2. At the top of the database, click the filter icon.
3. Select property 'author'.
4. Only one name will show up even if you have more names with the same property.

### Expected Behavior

When I select a property to filter, I expect all of the names with that property to show up in the database.

### Screenshots

https://github.com/user-attachments/assets/afd5a84b-22ff-4efb-a748-b032ad6e59b8

### Desktop or Mobile Platform Information

App Version: 2.0.1
Git Revision: b09316a
Platform: Mozilla/5.0 (Macintosh Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML like Gecko) Logseq/2.0.1 Chrome/148.0.7778.180 Electron/42.3.0 Safari/537.36
Language: en-US
Plugins: logseq-bullet-threading (v1.1.4), logseq-heatmap (v2.4.3), logseq-journals-calendar (v0.11.1), logseq-luma (0.3.1), logseq-markdown-table (v1.9.0), logseq-tabs (v1.19.4), logseq-wordcount-plugin (v2.4.3)

### 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 filtering sequence in the issue using an author property with multiple names, then compare it with fixed-option properties such as status or priority. Done means selecting one author filter shows every matching name, repeated filters do not change the result unexpectedly, and removing one filter does not remove both.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.