Architectural decision
RLSstorageauth🟢SQLI'm doing an mvp project and use supabase as my whole backend. I'm a beginner in SQL. My app is getting a little complicated and so is writing RLS and triggers. Also I have no idea how to test those things. I was thinking about moving this logic to code since I would feel way more comfortable there.
I chose supabase mainly because of auth and file storage.
Should I create a middle api layer (with c# asp .net) between my client and supabase?
If yes, how to do it? Disable all RLS?
I chose supabase mainly because of auth and file storage.
Should I create a middle api layer (with c# asp .net) between my client and supabase?
If yes, how to do it? Disable all RLS?
