-
Notifications
You must be signed in to change notification settings - Fork 177
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.
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
Not Equal filter returns data that matches the filter (neq) #575
Comments
I don't quite get you - does the first record not have a related record in |
It seems like you are encountering an issue with the Supabase query filter not working as expected, specifically with the neq (not equal) filter on a foreign table. The problem might be related to how Supabase handles the filtering on nested fields. One potential solution is to use the is or is_not filter for explicit comparison with None on the dashboard_client.classification field.
|
No reply from OP for over 5 months now. Closing this one out. |
Describe the bug
I'm using supabase with django app, whenever I use neq filter over foriegn table it returns all data, only the data matches the filter returned with "None" on the filter key instead of being neglected at all
to be more clear:
data returned from this:
as you can see, first record should be filtered not returned with value None on
dashboard_client
fieldAm I using this client wrong?
The text was updated successfully, but these errors were encountered: