From 9c0db849ce6f46cd618555c5bd7b2375c724745c Mon Sep 17 00:00:00 2001 From: Wolfgang Walther Date: Thu, 3 Feb 2022 07:50:55 +0100 Subject: [PATCH] Move JSON Columns and Computed Columns sections one level up Both of those are about select and filters - so do not belong into "Vertical Filtering" only. Signed-off-by: Wolfgang Walther --- docs/api.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api.rst b/docs/api.rst index 6367d4a3b..92dd04fbe 100644 --- a/docs/api.rst +++ b/docs/api.rst @@ -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 `_. @@ -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: