isee thanks for clarification for last point -> it's bcs i m creating a note taking type of app where users can create acc and use create different section of notes public/private and i don't know how to structure db so i can keep all the notes with their proper dates and stuffs so im creating different table for different users so db is structure nosql is different from relational db so it's hard to think in terms of column based db as i m shifting from firebase

So, the way I'd handle this is have the user_id stored for each note. When a user wants to create a new note, their user_id is added alongside their note. You can then use row level security (in the policies tab in the dashboard), to restrict it, something like this should do it:

(id = uid()

oh isee that is lot more scalable and easier although i didn't get

id = uid()

what are we checking here ?

uid()

is a built in function inside Supabase. I've just checked my dashboard, and an example I have is:

(uid() = owned_by_user)

owned_by_user

is a column which includes the user ID

ooh isee thanks that is lot more simpler than making table for every user

No hard-coded limit, it's only limited by the amount of server resources (e.g. memory)

mhm alr thankyou again