From 1a9e105227f4e724814d57b4fe2f98c9dd803d6b Mon Sep 17 00:00:00 2001 From: steve-chavez Date: Wed, 28 Jun 2023 12:12:27 -0500 Subject: [PATCH] add headings to computed fields --- docs/references/api/computed_fields.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/references/api/computed_fields.rst b/docs/references/api/computed_fields.rst index 194a48f3c..5379d51d5 100644 --- a/docs/references/api/computed_fields.rst +++ b/docs/references/api/computed_fields.rst @@ -19,6 +19,9 @@ Computed fields are virtual columns that are not stored in a table. PostgreSQL m SELECT $1.first_name || ' ' || $1.last_name; $$ LANGUAGE SQL; +Horizontal Filtering on Computed Fields +======================================= + :ref:`h_filter` can be applied to computed fields. For example, we can do a :ref:`fts` on :code:`full_name`: .. code-block:: postgres @@ -43,6 +46,8 @@ Computed fields are virtual columns that are not stored in a table. PostgreSQL m {"first_name": "Samuel", "last_name": "Beckett", "job": "novelist"} ] +Vertical Filtering on Computed Fields +===================================== Computed fields won't appear on the response by default but you can use :ref:`v_filter` to include them: @@ -62,6 +67,8 @@ Computed fields won't appear on the response by default but you can use :ref:`v_ {"full_name": "Samuel Beckett", "job": "novelist"} ] +Ordering on Computed Fields +=========================== :ref:`ordering` on computed fields is also possible: