Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue with filtering using recursive O2M count #14338

Closed
goggi opened this issue Jul 8, 2022 · 2 comments · Fixed by #22297
Closed

Issue with filtering using recursive O2M count #14338

goggi opened this issue Jul 8, 2022 · 2 comments · Fixed by #22297
Labels
🍰 Bug

Comments

@goggi
Copy link

goggi commented Jul 8, 2022 •
edited by azrikahar

Describe the Bug

I'm trying to filter a recursive o2m field based on the count option that is available. But the filter is not filtering away records that I expect to be removed.

recording_20220708-231701.webm

The o2m relation is to itself
image

To Reproduce

See video

Errors Shown

No response

What version of Directus are you using?

9.14.1

What version of Node.js are you using?

16.15.0

What database are you using?

Postgres 13,

What browser are you using?

Firefox

How are you deploying Directus?

Docker
@eikaramba
Copy link
Contributor

i can also confirm this on sqlite with latest directus (9.14.1)

@azrikahar azrikahar changed the title Issues with filtering using o2m count options Issue with filtering using recursive O2M count Jul 11, 2022
@rijkvanzanten
Copy link
Member

Linear: ENG-233

@hanneskuettner hanneskuettner mentioned this issue Apr 23, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🍰 Bug
Projects
Software Roadmap
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix count helper function for self-referencing relations directus/directus
4 participants
@eikaramba @goggi @rijkvanzanten @azrikahar