Aha! https://nikofischer.com/supabase-how-to-query-users-table — create a public users table + a trigger to keep it updated! Sweet!

Be wary that the article is missing a vital step which could break this, if the user was to change their email, it won't be changed in the profiles table, you need to create another trigger to make sure that is kept up to date or make sure you make an additional call to update the email in the profiles table

ooo that's a good one! Thank you!

depending on you scenario you might not need to keep 2 tables in sync - just create a view in the public schema which references the users table in the auth schema. However, you still need to ensure that you don't leak user info to the wrong users (not sure if you can define RLS on the auth.users table, but even if you cannot, you can protect the data on the view definition level with an additional clause)

I don't think RLS work on views from what I remember, so yeah be careful of the data you make available in them

Indeed, you cannot define RLS for a view, however, as long as the definer of the view does NOT bypass RLS policies in general, the view will respect the RLS of the underlying table

When I run this function, a user is created as expected in the

users

table with a new UUID — but the returned value is

null.

let { user, error } = await supabase.auth.signIn({
        email: formData.get('email')
      })

Is there anyway to return the newly created user's UUID / user object from this function? (I have turned off "Enable email confirmations" in the auth settings, to make it easier)

@User can I DM you?

Yep...do I need to enable something? I tried DM-ing you but the message could not be delivered

This is more of a "what the hell is happening" kind of question, but when you create a new schema, add it via the dashboard and create a client to open a connection to that schema only, if you use the service role key do you have to grant usage and privileges to the appropriate role yourself? It seems like it, because I had to do this myself because supabase would keep sending 403 responses for every request I made. I tried this with the anonymous key too. What exactly does adding a schema via the dashboard do? This isn't enough explanation imo:

The schema to expose in your API. Tables, views and stored procedures in this schema will get API endpoints.public and storage are protected by default.

The bits in the blog post and the couple sentences in the docs don't do enough either imo What does it mean by "protected by default"? Does it have something to do with grants?

I'm trying to add rows to

profiles

table when new users are added, including metadata like

email address

,

name

,

website

, all through the initial sign up function. So creating a new user like this:

javascript
      const { data, error } = await supabase.auth.signIn(
        { email: localStorage.getItem('email') },
        {
          data: {
            full_name: formData.get('full_name'),
            introduction: formData.get('introduction'),
            website_url: formData.get('website_url'),
            linkedin_url: formData.get('linkedin_url'),
            twitter_handle: formData.get('twitter_handle'),
            contact_method: formData.get('contact_method')
        }
      })

And handling it like this:

sql
create function public.handle_new_profile()
returns trigger as $$
begin
    insert into public.profiles (user_id, user_email, full_name, introduction, website_url, linkedin_url, twitter_handle, contact_method )
    values (new.id, new.email, new.raw_user_meta_data->>'full_name', new.raw_user_meta_data->>'introduction', new.raw_user_meta_data->>'website_url', new.raw_user_meta_data->>'linkedin_url', new.raw_user_meta_data->>'twitter_handle', new.raw_user_meta_data->>'contact_method');
    return new;
end;
$$ language plpgsql security definer;

-- trigger the function every time a user is created
create trigger on_auth_user_created
  after insert on auth.users
  for each row execute procedure public.handle_new_profile();

Currently, new rows in

profiles

are created when the function is called — but they only contain the

user_id

and

user_email

fields, none of the other data. I feel like this might be some syntax error in the

public.handle_new_profile()

function, not receiving the user metadata or int it the right way. Can anybody suggest a troubleshoot/fix?

setting metadata when using magic link auth

hello guys, I am new to SupaBase and I have been fiddling with it for about an hour. I plan to use it along with a nodejs project. Now I wish to find the max value in a column but I couldn't find details about it in the documentation, so how can I pull out the max value from a select statement?

I have user Profiles in my app. It's got normal profile info, but I also want users to do a small quiz/survey thing and store that data.

I was thinking of storing it in json. When I load

/profile/

I fetch the fields and the blob of json, and template thatt back out as a quiz. Does that sound like a sensible thing to do?

Where to store quiz survey data

Hey all, I am curious about this: RLS is not working for realtime publications - does that mean any table I enable realtime on can be CRUD operated by any authenticated user? So if I enable realtime just to listen for inserts can any authenticated user delete or update my leaderboard or how would that work?

RLS doesn't work with realtime yet, but it's something the team are working to resolve. Subscriptions are read-only and don't enable changing of the data. Requests to CUD data still need to be done through the REST endpoint (which is what the client libraries use, or via any traditional SQL-based approach). RLS will apply to these methods.

great news! thank you. 🙂

have anyone used supabase in react native? i just wonder if i can login with providers like google or facebook

Yes, from what I understood you can do that.

i mean, will it open a new browser to do that?

Probably yes, as that is how it usually works in general.

yea i just wonder if it works on react native

ive used it on react before

thanks, ill give it a try

You're welcome! 🙂

Can someone show me how we can connect typeorm with supabase

Or have some example code