-
Notifications
You must be signed in to change notification settings - Fork 45
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
PGRST102: Error in $: not enough input when inserting data using supabase-py #305
Comments
Did you ever figure out a way to fix this? Been stuck in the same problem this week. |
Nope, no luck on my end. |
Hey @goodmarvin @Tyfee , Thanks for filing a bug report - can I check if you're still facing the issue? Let us know! Also going to transfer this to |
@J0 Had to move to a different database provider because I couldn't get this to work. Love Supabase for my node projects, but I've really had a tough time getting things to work as I'd like them in python. |
Anyone still facing this issue - can you enable debug logging and send the logs for the requests that httpx sends? I'm not able to reproduce this right now so it'd help give me some leads about what's causing this bug |
Also please make sure you're on the latest version of this package, AND that you haven't accidentally installed the wrong package. The latest version is installed with |
I'll be closing this now as I've not been able to reproduce this error with the latest version of this package - previous instances of people encountering this bug was due to the wrong package ( |
I had a similar issue. I had, in fact, installed |
Trying to update a row using the supabase.table().update().eq().execute() pattern. Using postman to test my API it keeps returning the error "PGRST102: Error in $: not enough input"
Googling this error, I came across a similar issue that popped up with the JS version of supabase. (There error that time was it seems that this happened because an exception during the JWT decoding caused cloudflare workers to resend the request without a body(hence the error message)"
The text was updated successfully, but these errors were encountered: