supabase.table('users').insert({"dao":str(member.guild.id),"username":str(member.name),"user_id":str(member.id)}).execute()
                         print(data3)

this is the insert qery

({'message': 'column users.uid does not exist', 'code': '42703', 'hint': 'Perhaps you meant to reference the column "users.id".', 'details': None}, None)

this is response, weird thing is im calling user_id not uid idk why its refrencing that

users table^

cool

?

Could you show us the full stacktrace?

Also, what is the type of the user_id column?

might be related to this https://discord.com/channels/839993398554656828/843999948717555735/927089073439518720

also the users table has a column dao that has foreign key to daos.uid

manually adding data thru the dashboard works

so u cn try it there

u cn copy the code into another file and try it

Maybe there's more details in the database logs? It looks like something is mixing up your public.users table with the predefined auth.users

@User ^

sorry, I'm not too sure about this one. Might not be a python lib issue per se @User @User @User wondering if y'all have any thoughts on this?

So when we construct a query we update

session.params

to include filters and the such

But when we

.execute

them, we don't clear the old params out

So in the next query, the params from the previous query are also sent

py
In [12]: client.from_("test").select("*").execute()
Out[12]:
([{'id': 7,
   'created_at': '2021-10-02T16:20:51+00:00',
   'names': 'Abcdef',
   'roll_numbers': '10115'}, ...

py
In [14]: client.from_("test").select("*").eq("non-existing-col", "1").execute()  # errors out as expected
Out[14]:
({'message': 'column test.non-existing-col does not exist',
  'code': '42703',
  'hint': None,
  'details': None},
 None)
In [15]: client.from_("test").select("*").eq("id", "1").execute() # SHOULDN'T error, but...
Out[15]:
({'message': 'column test.non-existing-col does not exist',
  'code': '42703',
  'hint': None,
  'details': None},
 None)

ahh that makes sense

have to dig through the API logs to catch it

What do I do now?

Any temporary fix ?

We'll work on it and publish a version w the solution since it's an important bug

Any tentative date on when the fix can be published?

Yeah sorry about the bugs, we're still in alpha unfortunately 😅 and thank you for taking the time to report your issues! It will go a long way towards improving the eventual user experience

😅

the js client is more mature

@leynier you’re a rock star man 🚀

@User is the previous bug of match func fixed, cos for this ill hv to update to latest version

And v0.2.0 fix this bug