Open vladgardus opened 1 year ago
same error here, with update
.
posteresti-js
v1.7.2
After investigating we notice that the problem was a computed field (in the select) that returns null
.
Rewrite .select('*, computed_field')
into .select('*, computed_field(*)')
solve the issue for us.
@vladgardus check if this is your case
FYI, Same here with udpate
, I fixed it by updating the policies.
Bug report
Describe the bug
I encountered this issue only when the edge function I'm using is deployed. I've written some code where I insert a record and a few lines of code after I update the same record. It happens sometimes that updates return this error:
This is in mainly the code compiled from multiple files:
What am I doing wrong?
It feels like those queries run in different transactions and the first one doesn't end after the insert.
Do I need to somehow destroy the supabase client after each edge function execution? This does not happen right after deploying the function, but after a couple of runs.