supabase | Follow to stay | Authentication library

Your code makes perfect sense. Your component cannot know the value of something that needs to be fetched on mount.

The classic way to handle that kind of situation is using a state as follow:

While I haven't used Supabase at all, it looks like it provides a Promise-based async request API.

In that case, you could use it with RTK Query's queryFn endpoint option, which lets you write your own arbitrary async logic and return whatever data you want.

While I haven't tested this code, a translation of the React Query + Supabase example to RTKQ might look like:

It looks like your match filter doesn't work.

I would suggest trying to match row by its ID since you want to update only one row. This way you are actually trying to update all rows that match this data, and that might be causing an issue. I am not sure if we can batch update like this with supabase at the moment.

This is something I'm using in my apps whenever I want to update data for a single row, and I don't have any issues with it. I would suggest to try this, if the question is still relevant. 😊

await supabase.from("company").update(inputFields).match({ id: company.id });

or

await supabase.from("company").update(inputFields).eq("id", company.id)

You could also pass only new values to .update() so you don't update whole row, but only data that has been changed.

A test case:

The way to store data in React components is to define and set state.

The correct place to handle side-effects like async response data is in an effect hook

This question was answered on GitHub

You have an extra .select() at end which fetches all columns...

Assuming the code using await is inside an async function (or at the top level of a module), the syntax is correct, but it's probably not what I'd use (in general, avoid mixing async/await with explicit callbacks via .then and .catch), and separately it's probably not working quite as you expect (this is borne out by your saying that your code was failing to delete from table-two).

For any particular id value, your code starts deleting from table-one and then immediately starts deleting from table-two without waiting for the deletion in table-one to complete:

There are multiple errors as you can see in the manual

The DECLARE section goes before the BEGIN.

And as documented in the manual the INSERT statement has no WHERE clause.

So assuming you have the rest of the function (or procedure) right (which you didn't show us, the PL/pgSQL block needs to look like this:

You can try the Supabase Adder: https://github.com/supabase-community/svelte-supabase