Also shoutout to three.js for having an incredible variety of examples and great documentation to learn from. And credit to mixamo for the android-esque robot model.
Feedback and suggestions welcome! :)
Also shoutout to three.js for having an incredible variety of examples and great documentation to learn from. And credit to mixamo for the android-esque robot model.
Feedback and suggestions welcome! :)
Leveraging most RDBMS security features seem to be geared for an ever shrinking set of use cases where a mostly static set of users are given direct access to a SQL prompt, or a simple record to GUI application interface.
Regarding database connections -- one way to avoid needing a connection per user is to use something like PostgREST[2] to handle incoming requests, identify the user making the request, and use an existing db pool connection to switch roles and execute whatever queries are requested. EDIT: RedShift1 beat me to this explanation by a little bit! :)
RLS certainly isn't the answer for every domain or problem size, but I've been surprised by how powerful it is compared with how relatively unknown it is.
[1]: https://supabase.com/blog/2021/03/31/supabase-cli#migrations
[2]: https://postgrest.org/en/stable/auth.html