jimmy/postgrest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

bring back schema isolation on its own page

Browse Source
This commit is contained in:
steve-chavez
2023-12-01 19:03:23 -05:00
committed by Steve Chavez
parent 2b4e0cc10a
commit 70c0d88fa7
2 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/explanations/db_authz.rst
+1 -10
View File
@@ -92,19 +92,10 @@ You can mix the group and individual role policies. For instance we could still
-- allow authenticator to switch into user000 role
-- (the role itself has nologin)
.. _schema_isolation:
Schemas
=======
A PostgREST instance exposes all the tables, views, and stored procedures of the schemas configured in :ref:`db-schemas`. This means private data or implementation details can go inside private schemas and be invisible to HTTP clients.
It is recommended that you don't expose tables on the schemas you expose, instead expose views and stored procedures which insulate the internal details from the outside world.
This allows you to change the internals of your schema and maintain backwards compatibility. It also keeps your code easier to refactor, and provides a natural way to do API versioning.
.. image:: ../_static/db.png
You must explicitly allow roles to access the exposed schemas:
You must explicitly allow roles to access the exposed schemas in :ref:`db-schemas`.
.. code-block:: postgres