Skip to content

Docs: Clarified the behavior of message filtering in the query #277

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

Open
stromhalm wants to merge 2 commits into
base: main
Choose a base branch
from
+2 −2
Open

Docs: Clarified the behavior of message filtering in the query #277

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
56b44ee
Clarified the behavior of message filtering in the query
stromhalm Dec 13, 2025
9fdbba7
Docs: Added missing closing parenthesis for .filter(...)
stromhalm Dec 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions npm-packages/docs/docs/database/reading-data/indexes/indexes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,13 +204,13 @@ do:
const messages = await ctx.db
.query("messages")
.withIndex("by_channel", q => q.eq("channel", channel))
.filter(q => q.neq(q.field("user"), myUserId)
.filter(q => q.neq(q.field("user"), myUserId))
.collect();
```

In this case the performance of this query will be based on how many messages
are in the channel. Convex will consider each message in the channel and only
return the messages where the `user` field matches `myUserId`.
return the messages where the `user` field doesn't match `myUserId`.

## Sorting with indexes

Expand Down