You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm pretty sure the filter operators null and notnull aren't working. I don't think they are understood once they are passed through to mikroorm for execution.
I have tried running a filter like { council_null: true } where council is a field on an entity, and it throws an error as mikroorm tries to prepare the SQL query
To Reproduce
Steps to reproduce the behavior:
Set up a query with a filter using a _null suffix
Execute the query
The query fails at runtime
Expected behavior
The documented filter operators should all be supported
Actual behavior
What actually happened.
Screenshots or Screencasts
If applicable, add screenshots or screencasts to help explain the issue.
Desktop (please complete the following information):
OS and version: [e.g. MacOS 13.3.1, Windows 11 v22H2]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm pretty sure the filter operators
null
andnotnull
aren't working. I don't think they are understood once they are passed through tomikroorm
for execution.The set of available files that should be supported are listed at https://graphweaver.com/docs/filters-and-operators
The mikroorm filter syntax docs are here https://mikro-orm.io/docs/query-conditions, and there's no mention of null handling
I have tried running a filter like
{ council_null: true }
where council is a field on an entity, and it throws an error as mikroorm tries to prepare the SQL queryTo Reproduce
Steps to reproduce the behavior:
Expected behavior
The documented filter operators should all be supported
Actual behavior
What actually happened.
Screenshots or Screencasts
If applicable, add screenshots or screencasts to help explain the issue.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: