Realm used to be just their real time database, while Stitch was their supabase-like offering, but it looks like they're merged now

I've used Stitch to great enjoyment, but most of the reasons I used Mongo over SQL don't exist with Supabase

namely that refactoring and migrating schemas is a nightmare but Supabase makes it painless

i just created this function and trigger:

create function public.handle_new_user() 
returns trigger as $$
begin
  insert into public.users (user_id, name, surname)
  values (new.id, new.raw_user_meta_data.first_name, new.raw_user_meta_data.last_name);
  return new;
end;
$$ language plpgsql security definer;
create trigger on_auth_user_created
  after insert on auth.users
  for each row execute procedure public.handle_new_user();

but now i wanna delete both

i can see the function in the "functions" section of the dashboard

but not the trigger

and i can't delete the function without first deleting the trigger i believe

nvm, i believe i got it with:

DROP FUNCTION public.handle_new_user() CASCADE

hopefully i didn't broke anything else by doing it

Can I get the

raw_user_meta_data

via the function? If so, how? I tried and I was getting an Error trying to insert.

nvm, i got it aswell, it was a syntax error

just had to change it to:

values (
    new.id, 
    new.raw_user_meta_data->>'first_name', 
    new.raw_user_meta_data->>'last_name'
  );

@User how are you getting that to work

are you passing first name and last name as the options object with the email signup method?

did https://app.supabase.io/api/login get yeeted? I'm trying to log in through vercel's integration and keep getting a 404

I have a question regarding supabase-auth and different server urls (e.g. in feature branches) Lets assume my main page runs on

example.com

and I have a feature branch

my-cool-fature.example-app.vercel.com

- What do I need todo so that the emails from the feature branchs are pointing to that branch URL? (For example magic-link login, etc?)

gotta pass another object to the signup method with the data

it'd look something like this:

const { user, session, error } = await supabase.auth.signUp(
  {
    email: 'example@email.com',
    password: 'example-password',
  },
  {
    data: { 
      first_name: 'John', 
      age: 27,
    }
  }
)

Hey everyone, I have a very dumb question / problem you can probably help me with ... Let's say I have a table with a column name, and another last name. And I don't want to have to rows with the same combination of name-last name (duplicates) What would be the easiest way to reject post requests trying to add a duplicate or to clean duplicates periodically?

You can create a unique constraint on the the table so that the combination of those two values is always unique.

is it normal that when I try to add a column to a table I get

cannot drop constraint profiles_pkey on table profiles because other objects depend on it

it is only update and I have done this 2-3 days ago with other columns, but not today for some reason

hm when doing the same thing (add column) from the

+

button on the end of the table, it works...

I feel like I was doing exactly what your doing and it wasn’t working. I guess I’ll try again.

what were you trying to do?

Add a full name field to profile table from raw user meta data.

On signup

oh, gotta create a function and trigger for that

Yeah, I have one of those. I can only think some how I got the syntax wrong. I’ll have to give it another try.

Thank you!