Does upsert() support composite keys? It doesn't seem the table editor does

Im wondering if how will I use auth.uid() to ensure that the post or comment that one being created/inserted is the actual id of the user and not of the other?

RLS policy on insert:

(uid() = user_id)

(if

user_id

is the name of the column where the user ID is stored)

I have another question. Can i omit passing the userId on the DTO but use the auth.uid to insert the post along side with other details of the post?

You should be able to do it with a postgres

BEFORE INSERT

trigger. The function that's triggered could do something like this:

sql
INSERT INTO public.some_table (column_1, is_public, user_id)
VALUES ("Some string value", true, auth.uid());

That's assuming that

user_id

isn't nullable. If it's allowed to be nullable, then an after insert trigger could do the same job

Yes it isnt nullable :)

What would u prefer off the two??

Im honestly new to triggers and policies thats why 😅

It depends on the use-case, but if I've got the option to insert it before, I'll take that route. You can also pass things like

new.some_value

as values, which are useful if the trigger is running on a `BEFORE INSERT`:

sql
CREATE OR REPLACE FUNCTION public.insert_article()
RETURNS trigger
LANGUAGE plpgsql
SECURITY DEFINER AS $$
begin
  INSERT INTO public.some_table
    (column_1, is_public, user_id, article_title, article_date)
  values
    ('some string value', true, auth.uid(), new.article_title, new.article_date);
  return new;
end;
$$;

(That specific example might need some tweaking to work, but the general idea is there)

Thanks @User 🙂

On that topic, I strongly suggest handling that kind of inserts/updates via your own backend

I assume you would want some checks/sanitization which would be a pain to implement at pgsql level

Unless it’s a simple text only post with not much going on

I'll keep this in mind.. Yeah ur right. But right now as much as possible really im trying to make supabase a go to solution ignoring creating custom backend first.

If i have a user that signed up via 3rd party provider..

How can I link a password with that existing account?

You just set the password with the Supabase SDK

All accounts are linked by email by default iirc

Same goes in reverse. If you create an email:password account, you can login with a third party provider if the account uses the same email

Finally found it!!

dart
final userAttributes = UserAttributes(password: _password);
        final response =
            await Supabase.instance.client.auth.update(userAttributes);

dang im looking

dart
Supabase.instance.client.auth.changePassword('');

Same! I'm waiting for it too, Want to self host and use it.

How do we go about upgrading postgres versions to the latest supported by supabase? Or must we create a new project, and migrate to the new project?

Upgrade Postgres to latest version

What is the suggested way to duplicate a database for more than one environment? Say prod and dev. If we already have a built out prod DB how can I best keep a dev version in sync?

What is the font supabase uses on the logo?

Upsert composite keys

thanks mate

can you trigger an api call from triggers+functions?