Supabase is an open source Firebase alternative. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, and Storage.

Supabase

The reason I ask is - In the documentation I read ```The auth.users table has a JSONB column called raw_user_meta_data``` however this is problematic because if a new signUp is called on an email address that already exists it will overwrite the metadata

This shouldn't be the case, because if the email already exists then the account  wouldn't be created again

If this is happening then its definitely a bug and should be reported

ya its def happening I just tested it for a good 10 times. It happens on email validated accounts too

```    const { user, session, error } = await supabase.auth.signUp({
        email: email,
        password: password,
    },{
        data:{
            phone: phone,
            name: name,
            company: company
        }
    })```

the password luckily is not overwritten 🙃

On this repo https://github.com/supabase/supabase-js

Although its a bug, do remember to not store data inside the `metadata` object, but rather use it as a transport object, it's best to write that data to a table as soon as possible

Unfortunately I can't even prevent it because there is no API to check if a user exists 😕

Funny you mention this, this is something I'm working on now for a project I'm working on

ya there's only a work-around of using a profiles table which is not ideal and immediately takes away from the 'easy auth solution' pitch

The profiles table is a part of the easy auth solution pitch

is there a way to know if a user has validated their email

You can check the email_confirmed_at field inside the auth.users table, but you can't do this directly inside of the supabase-js library

It would be best to create a view with the `id, email, email_confirmed_at` and then query against that

```sql
CREATE VIEW public.list_users AS
SELECT id, email, email_confirmed_at
FROM auth.users
```

Now with the supabase-js library you can do
```js
const {data, error} = await supabase.from('list_users').select('*').eq('email', 'email_you_wish_to_check_here');

// now you can check email_confirmed_at inside of data
console.log({ data });
```

Do note though that this table is not protected by RLS, so it shouldn't contain sensitive data or data you don't want anyone who is not logged in to access

The other option is to create a Postgres function to do this and get the value back from that

ya I will just build a server-side api that uses the service account to talk to the auth.users table