Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 5bb9ba2

Browse files
committed
Doc: alphabetize aggregate function table
A few recent JSON aggregates have been added without much consideration to the existing order. Put these back in alphabetical order (with the exception of the JSONB variant of each JSON aggregate). Author: Wolfgang Walther <walther@technowledgy.de> Reviewed-by: Marlene Reiterer <marlene.reiterer.03@gmail.com> Discussion: https://postgr.es/m/6a7b910c-3feb-4006-b817-9b4759cb6bb6%40technowledgy.de Backpatch-through: 16, where these aggregates were added
1 parent fefa76f commit 5bb9ba2

File tree

1 file changed

+48
-48
lines changed

1 file changed

+48
-48
lines changed

doc/src/sgml/func.sgml

Lines changed: 48 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -21925,6 +21925,54 @@ SELECT NULLIF(value, '(none)') ...
2192521925
<entry>No</entry>
2192621926
</row>
2192721927

21928+
<row>
21929+
<entry role="func_table_entry"><para role="func_signature">
21930+
<indexterm>
21931+
<primary>json_agg_strict</primary>
21932+
</indexterm>
21933+
<function>json_agg_strict</function> ( <type>anyelement</type> )
21934+
<returnvalue>json</returnvalue>
21935+
</para>
21936+
<para role="func_signature">
21937+
<indexterm>
21938+
<primary>jsonb_agg_strict</primary>
21939+
</indexterm>
21940+
<function>jsonb_agg_strict</function> ( <type>anyelement</type> )
21941+
<returnvalue>jsonb</returnvalue>
21942+
</para>
21943+
<para>
21944+
Collects all the input values, skipping nulls, into a JSON array.
21945+
Values are converted to JSON as per <function>to_json</function>
21946+
or <function>to_jsonb</function>.
21947+
</para></entry>
21948+
<entry>No</entry>
21949+
</row>
21950+
21951+
<row>
21952+
<entry role="func_table_entry"><para role="func_signature">
21953+
<indexterm><primary>json_arrayagg</primary></indexterm>
21954+
<function>json_arrayagg</function> (
21955+
<optional> <replaceable>value_expression</replaceable> </optional>
21956+
<optional> <literal>ORDER BY</literal> <replaceable>sort_expression</replaceable> </optional>
21957+
<optional> { <literal>NULL</literal> | <literal>ABSENT</literal> } <literal>ON NULL</literal> </optional>
21958+
<optional> <literal>RETURNING</literal> <replaceable>data_type</replaceable> <optional> <literal>FORMAT JSON</literal> <optional> <literal>ENCODING UTF8</literal> </optional> </optional> </optional>)
21959+
</para>
21960+
<para>
21961+
Behaves in the same way as <function>json_array</function>
21962+
but as an aggregate function so it only takes one
21963+
<replaceable>value_expression</replaceable> parameter.
21964+
If <literal>ABSENT ON NULL</literal> is specified, any NULL
21965+
values are omitted.
21966+
If <literal>ORDER BY</literal> is specified, the elements will
21967+
appear in the array in that order rather than in the input order.
21968+
</para>
21969+
<para>
21970+
<literal>SELECT json_arrayagg(v) FROM (VALUES(2),(1)) t(v)</literal>
21971+
<returnvalue>[2, 1]</returnvalue>
21972+
</para></entry>
21973+
<entry>No</entry>
21974+
</row>
21975+
2192821976
<row>
2192921977
<entry role="func_table_entry"><para role="func_signature">
2193021978
<indexterm><primary>json_objectagg</primary></indexterm>
@@ -22035,31 +22083,6 @@ SELECT NULLIF(value, '(none)') ...
2203522083
<entry>No</entry>
2203622084
</row>
2203722085

22038-
<row>
22039-
<entry role="func_table_entry"><para role="func_signature">
22040-
<indexterm><primary>json_arrayagg</primary></indexterm>
22041-
<function>json_arrayagg</function> (
22042-
<optional> <replaceable>value_expression</replaceable> </optional>
22043-
<optional> <literal>ORDER BY</literal> <replaceable>sort_expression</replaceable> </optional>
22044-
<optional> { <literal>NULL</literal> | <literal>ABSENT</literal> } <literal>ON NULL</literal> </optional>
22045-
<optional> <literal>RETURNING</literal> <replaceable>data_type</replaceable> <optional> <literal>FORMAT JSON</literal> <optional> <literal>ENCODING UTF8</literal> </optional> </optional> </optional>)
22046-
</para>
22047-
<para>
22048-
Behaves in the same way as <function>json_array</function>
22049-
but as an aggregate function so it only takes one
22050-
<replaceable>value_expression</replaceable> parameter.
22051-
If <literal>ABSENT ON NULL</literal> is specified, any NULL
22052-
values are omitted.
22053-
If <literal>ORDER BY</literal> is specified, the elements will
22054-
appear in the array in that order rather than in the input order.
22055-
</para>
22056-
<para>
22057-
<literal>SELECT json_arrayagg(v) FROM (VALUES(2),(1)) t(v)</literal>
22058-
<returnvalue>[2, 1]</returnvalue>
22059-
</para></entry>
22060-
<entry>No</entry>
22061-
</row>
22062-
2206322086
<row>
2206422087
<entry role="func_table_entry"><para role="func_signature">
2206522088
<indexterm>
@@ -22168,29 +22191,6 @@ SELECT NULLIF(value, '(none)') ...
2216822191
<entry>No</entry>
2216922192
</row>
2217022193

22171-
<row>
22172-
<entry role="func_table_entry"><para role="func_signature">
22173-
<indexterm>
22174-
<primary>json_agg_strict</primary>
22175-
</indexterm>
22176-
<function>json_agg_strict</function> ( <type>anyelement</type> )
22177-
<returnvalue>json</returnvalue>
22178-
</para>
22179-
<para role="func_signature">
22180-
<indexterm>
22181-
<primary>jsonb_agg_strict</primary>
22182-
</indexterm>
22183-
<function>jsonb_agg_strict</function> ( <type>anyelement</type> )
22184-
<returnvalue>jsonb</returnvalue>
22185-
</para>
22186-
<para>
22187-
Collects all the input values, skipping nulls, into a JSON array.
22188-
Values are converted to JSON as per <function>to_json</function>
22189-
or <function>to_jsonb</function>.
22190-
</para></entry>
22191-
<entry>No</entry>
22192-
</row>
22193-
2219422194
<row>
2219522195
<entry role="func_table_entry"><para role="func_signature">
2219622196
<indexterm>

0 commit comments

Comments
 (0)