From 8d4bc76aab358eb50d6ef61f2d9bceffa6f1e0ae Mon Sep 17 00:00:00 2001 From: steve-chavez Date: Mon, 26 Jul 2021 02:46:44 -0500 Subject: [PATCH] Add entry for OPTIONS on views * Also clarify the schema cache page --- releases/upcoming.rst | 6 ++++-- schema_cache.rst | 5 ++++- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/releases/upcoming.rst b/releases/upcoming.rst index 7c86d907e..fde6b391d 100644 --- a/releases/upcoming.rst +++ b/releases/upcoming.rst @@ -37,6 +37,9 @@ Added * Allow ``Bearer`` with and without capitalization as authentication schema. See :ref:`client_auth`. |br| -- `@wolfgangwalther `_ +* Allow OPTIONS to generate HTTP methods based on views triggers. See :ref:`OPTIONS requests `. + |br| -- `@laurenceisla `_ + * Show timestamps for server diagnostic information. See :ref:`pgrst_logging`. |br| -- `@steve-chavez `_ @@ -54,8 +57,7 @@ Added * Documentation improvements - + Added the :ref:`OPTIONS requests ` section. - + Added the :ref:`schema_cache` section. + + Added the :ref:`schema_cache` page. + Moved the :ref:`schema_reloading` reference from :ref:`admin` to :ref:`schema_cache` Fixed diff --git a/schema_cache.rst b/schema_cache.rst index df8804d21..e03359a8c 100644 --- a/schema_cache.rst +++ b/schema_cache.rst @@ -3,7 +3,10 @@ Schema Cache ============ -PostgREST caches metadata from the database schema to avoid repeating expensive queries. This metadata is not required by all of the PostgREST features, only the following: +Certain PostgREST features require metadata from the database schema. Getting this metadata requires executing expensive queries, so +in order to avoid repeating this work, PostgREST uses a schema cache. + +The following features are the ones that require metadata from the schema cache. +--------------------------------------------+-------------------------------------------------------------------------------+ | Feature | Required Metadata |