@@JonMeyers thansk for the appreciation. I would call myself an ambassador for supabase here in Denmark. Huge fan of the product, thanks to all at supabase for creating such a powerfull tool!
How do you handle different user types, for example employee and employer? I get all of that RLS stuff, but how do I get the user's type without doing left joins every time to display different UIs?
at a glance, the auth hooks seems like it would make it easier to set up role based auth (admin, employee, ...). Would this be a good way to do it? How would this work with the Next JS/SSR packages?
When using google sign in I have to allow permission everytime I sign In, where as on other apps when user goes into google & selects their emails they immediately get redirected to app, it doesn't ask permission again except for the first time. Whereas in Supabase it asks permission everytime. Any thought on optimising this? THanks
The real power of postgREST (Supabase's query builder) is that it pipes through the user's session to queries to the database. Combining RPC with views and postgres functions allows you to do pretty much anything postgres is capable of doing! Would a video on this be helpful?
@@JonMeyers Hell yeah✊... PS: have 3 tables: User; friend; contact; contact columns: user_id AND friend_id.... friend columns: friend_1 AND friend_2 (symmetrical friends many to many relation, one user can have many users as friends); how to join contacts, all the way to user(friend's profile) THROUGH friend (where friend_1 auth.uid() OR friend_2 auth uid())
probably some time next year - we still have to get to a bunch of other features like anonymous logins, complete support for webhooks and OIDC for mobile before we think about passkeys 😅