[Auth] Add search/filter by user id inside Auth table

[iosephmagno]

Due to bug supabase/auth#1629, user failed to change his phone number. After several attempt using different phone numbers, the phone number eventually changed to a new one, but that was not the correct one. As consequence of that, the phone number inside table public.users is wrong for this user and we cannot understand what is the user's phone number registered to Auth table because Auth table cannot be filtered by user id. Adding search/filter by user id would help fix this case and would be helpful in general anyway We would appreciate if the feature could be added with upcoming releases.

[GaryAustin1]

For now you can go the table UI. Select auth schema, and the users table. Then use the filters there to filter the phone column.

[iosephmagno]

supabase/auth#1629

supabase/auth#1627

[GaryAustin1]

My only comment on public.users is that you are responsible for all updates/deletions etc. on it. If the user row is gone from the auth.users table then either you have to delete, or cascade delete has to take care of it if set up correctly. If phone numbers change you have to have an update trigger to update public.users if you keep the phone numbers there.

I can't comment on your auth reports themselves. I don't use phone numbers for users.

[GaryAustin1]

I'm not sure that your public.users table is not part of the issue.
You should look at the Postgres logs when you get the error.
If you delete a user and their row stays in your public users table with the phone number there, then when you try to signup again you could get an error if the phone number column is marked unique.

You say there are rows in the public.users table with UUID's that are not in auth.users table. That is not good for the typical public.users table and can lead to all kinds of failures if you check that any data has to be unique in that table.

[iosephmagno]

Are you sure that auth id is public.users id, coz you suggested that in a comment above but it doesnt seem so. In any events, our reported issues are correct.

[GaryAustin1]

I have no idea what is in public.users. That is a table you created. auth.users is Supabase's table that I showed and should match the authenticated tab table that highlights it.

[iosephmagno]

Please check above issues. Auth is buggy, if you dont signup user via otp codes you might not experience issues.