From 9f15044e63ecbf2c91fd6e59ba932804fcb35bcb Mon Sep 17 00:00:00 2001
From: Wolfgang Walther <walther@technowledgy.de>
Date: Sun, 22 Nov 2020 21:33:37 +0100
Subject: [PATCH] Add note about embedding of view-chains and the interaction
 with `db-extra-search-path`

---
 api.rst | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/api.rst b/api.rst
index 9303d9528..d2119a6ea 100644
--- a/api.rst
+++ b/api.rst
@@ -670,7 +670,7 @@ As an example, let's create a view called ``nominations_view`` based on the *nom
   FROM
     nominations;
 
-Since it contains ``competition_id`` and ``film_id``—and each one has a **foreign key** defined in its source table—we can embed *competitions* and *films*:
+Since it contains ``competition_id`` and ``film_id`` — and each one has a **foreign key** defined in its source table — we can embed *competitions* and *films*:
 
 .. code-block:: http
 
@@ -697,6 +697,13 @@ It's also possible to embed `Materialized Views <https://www.postgresql.org/docs
 
 .. _s_proc_embed:
 
+.. _embedding_view_chains:
+
+Embedding Chains of Views
+-------------------------
+
+Views can also depend on other views, which in turn depend on the actual source table. For PostgREST to pick up those chains recursively to any depth, all the views must be in the search path, so either in the exposed schema (:ref:`db-schema`) or in one of the schemas set in :ref:`db-extra-search-path`. This does not apply to the source table, which could be in a private schema as well. See :ref:`schema_isolation` for more details.
+
 Embedding on Stored Procedures
 ------------------------------