-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
eq not working on apikey
column
#5465
Comments
I think this happens because the Kong gateway(reached before PostgREST on Supabase instances) uses the Not ideal, but a workaround could be renaming your |
Thanks, It resolved but its really bad. I spent so much time banging my head to wall 😁 |
I've documented it for now, eventually we will move |
Bug report
Supabase eq not working
Describe the bug
My data for select is
This is how I created the table
It's working for all the other keys but not apikey say
email.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Please create above table and add data give above
Expected behavior
0 Rows should be returned as no rows in db matches
no-apikey-db
. Buteq
returns all the rowsA clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
System information
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: