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

Move JSON Columns and Computed Columns sections one level up

Browse Source 
Both of those are about select and filters - so do not belong into "Vertical Filtering" only.

Signed-off-by: Wolfgang Walther <walther@technowledgy.de>
This commit is contained in:
Wolfgang Walther
2022-02-04 22:31:28 +01:00
committed by Wolfgang Walther
parent 71dd891d2f
commit 9c0db849ce
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/api.rst
+2 -2
View File
@@ -270,7 +270,7 @@ Casting the columns is possible by suffixing them with the double colon ``::`` p
.. _json_columns:
JSON Columns
~~~~~~~~~~~~
------------
You can specify a path for a ``json`` or ``jsonb`` column using the arrow operators(``->`` or ``->>``) as per the `PostgreSQL docs <https://www.postgresql.org/docs/current/functions-json.html>`_.
@@ -351,7 +351,7 @@ Note that ``->>`` is used to compare ``blood_type`` as ``text``. To compare with
.. _computed_cols:
Computed Columns
~~~~~~~~~~~~~~~~
----------------
Filters may be applied to computed columns(**a.k.a. virtual columns**) as well as actual table/view columns, even though the computed columns will not appear in the output. For example, to search first and last names at once we can create a computed column that will not appear in the output but can be used in a filter: