The point is that why they even have to make new users table? Something is driving them in this direction and as a counterexample you have Pocketbase where you don't have to.
To store application-specific data about users. The Supabase doc or examples show this. Where else would you put such data?
But what the docs don't cover is the provided Users table. Missing documentation is why I gave up on Supabase; and the Users table was one of the first problems I encountered. I could find no details on what to expect in each column at any given time.
Upon creating a new user, values get set in this table for no apparent reason. So if your application depends on knowing the verification status of a new user (for example), good luck... Supabase claimed every user was verified upon creation.
The auth schema is intentionally not exposed to the rest api for security reasons. You need to use an auth hook to put data where you need, or an RPC with appropriate privileges, and of course RLS on any tables.
You are right about the case studies, they are supposed to be centered but at this point, I am not sure if this is even a good way to preview the case studies.
Our company website is using a monologue with Discord messages to showcase our services. We're seeking honest feedback and ideas on how it can be improved. What are your thoughts?
I'm sharing a CV/Resume template for those of you who will be searching for jobs in 2024. I originally created it for friends and over time, six people have applied with it and started working. So, I thought it might be best to share it so that more people can use it.
reply