Add 'not' operator to filters #231
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
peterkelly
force-pushed
the
filter-not
branch
3 times, most recently
from
b991085 to
2b39683
Compare
peterkelly
force-pushed
the
filter-not
branch
2 times, most recently
from
e70c485 to
a8eaac6
Compare
Seaography already supports 'and' and 'or' operators on filters. This
commit adds a 'not' operator, which takes a filter object as an argument
and maps this onto the corresponding Condition not() method in SeaORM.
This is particularly useful for using operators that do not have an
inverse version, such as array contains. For example, in one use case,
we want to select all entities whose tags field does _not_ contain a
specific value:
{
runs(filters: {
not: { tags: { array_contains: ["disabled"] } }
}) {
nodes {
id
name
status
}
}
}
peterkelly
force-pushed
the
filter-not
branch
from
a8eaac6 to
df0c30b
Compare
tyt2y3
pushed a commit
that referenced
this pull request
Oct 27, 2025
Seaography already supports 'and' and 'or' operators on filters. This
commit adds a 'not' operator, which takes a filter object as an argument
and maps this onto the corresponding Condition not() method in SeaORM.
This is particularly useful for using operators that do not have an
inverse version, such as array contains. For example, in one use case,
we want to select all entities whose tags field does _not_ contain a
specific value:
{
runs(filters: {
not: { tags: { array_contains: ["disabled"] } }
}) {
nodes {
id
name
status
}
}
}
tyt2y3
pushed a commit
that referenced
this pull request
Oct 27, 2025
Seaography already supports 'and' and 'or' operators on filters. This
commit adds a 'not' operator, which takes a filter object as an argument
and maps this onto the corresponding Condition not() method in SeaORM.
This is particularly useful for using operators that do not have an
inverse version, such as array contains. For example, in one use case,
we want to select all entities whose tags field does _not_ contain a
specific value:
{
runs(filters: {
not: { tags: { array_contains: ["disabled"] } }
}) {
nodes {
id
name
status
}
}
}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Seaography already supports
andandoroperators on filters. This commit adds anotoperator, which takes a filter object as an argument and maps this onto the corresponding Condition not() method in SeaORM.This is particularly useful for using operators that do not have an inverse version, such as array contains. For example, in one use case, we want to select all entities whose tags field does not contain a specific value: