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

More improvements

Browse Source 
When to use RAISE in procs

Fix broken links
This commit is contained in:
Joe Nelson
2017-03-26 16:05:12 -07:00
parent e54fb2a264
commit 0f87137387
3 changed files with 38 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
auth.rst
+3 -1
View File
@@ -270,7 +270,7 @@ PostgREST aims to do one thing well: add an HTTP interface to a PostgreSQL datab
Schema Isolation
================
A PostgREST instance is configured to expose all the tables, views, and stored procedures of a single schema specified in a server configuration file. This means private data or implementation details can go inside a private schema and be invisible to HTTP clients. You can then expose views and stored procedures which insulate the internal details from the outside world. It keeps you code easier to refactor, and provides a natural way to do API `versioning`_. For an example of wrapping a private table with a public view see the `Editing User Info`_ section below.
A PostgREST instance is configured to expose all the tables, views, and stored procedures of a single schema specified in a server configuration file. This means private data or implementation details can go inside a private schema and be invisible to HTTP clients. You can then expose views and stored procedures which insulate the internal details from the outside world. It keeps you code easier to refactor, and provides a natural way to do API versioning. For an example of wrapping a private table with a public view see the :ref:`public_ui` section below.
SQL User Management
===================
@@ -363,6 +363,8 @@ With the table in place we can make a helper to check a password against the enc
end;
$$;
.. _public_ui:
Public User Interface
---------------------