docs: specify FOR UPDATE/SHARE incompatibilities
Document that FOR UPDATE/SHARE are incompatible with GROUP BY, DISTINCT, HAVING and window functions. Michael Paquier
This commit is contained in:
parent
fc4ffba968
commit
8824b38909
@ -654,6 +654,12 @@ GROUP BY <replaceable class="parameter">expression</replaceable> [, ...]
|
|||||||
the grouped columns (or a subset thereof) are the primary key of
|
the grouped columns (or a subset thereof) are the primary key of
|
||||||
the table containing the ungrouped column.
|
the table containing the ungrouped column.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Currently, <literal>FOR NO KEY UPDATE</>, <literal>FOR UPDATE</>,
|
||||||
|
<literal>FOR SHARE</> and <literal>FOR KEY SHARE</> cannot be
|
||||||
|
specified with <literal>GROUP BY</literal>.
|
||||||
|
</para>
|
||||||
</refsect2>
|
</refsect2>
|
||||||
|
|
||||||
<refsect2 id="SQL-HAVING">
|
<refsect2 id="SQL-HAVING">
|
||||||
@ -690,6 +696,12 @@ HAVING <replaceable class="parameter">condition</replaceable>
|
|||||||
within aggregate functions. Such a query will emit a single row if the
|
within aggregate functions. Such a query will emit a single row if the
|
||||||
<literal>HAVING</literal> condition is true, zero rows if it is not true.
|
<literal>HAVING</literal> condition is true, zero rows if it is not true.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Currently, <literal>FOR NO KEY UPDATE</>, <literal>FOR UPDATE</>,
|
||||||
|
<literal>FOR SHARE</> and <literal>FOR KEY SHARE</> cannot be
|
||||||
|
specified with <literal>HAVING</literal>.
|
||||||
|
</para>
|
||||||
</refsect2>
|
</refsect2>
|
||||||
|
|
||||||
<refsect2 id="SQL-WINDOW">
|
<refsect2 id="SQL-WINDOW">
|
||||||
@ -824,6 +836,12 @@ UNBOUNDED FOLLOWING
|
|||||||
than one window function.
|
than one window function.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Currently, <literal>FOR NO KEY UPDATE</>, <literal>FOR UPDATE</>,
|
||||||
|
<literal>FOR SHARE</> and <literal>FOR KEY SHARE</> cannot be
|
||||||
|
specified with <literal>WINDOW</literal>.
|
||||||
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Window functions are described in detail in
|
Window functions are described in detail in
|
||||||
<xref linkend="tutorial-window">,
|
<xref linkend="tutorial-window">,
|
||||||
@ -920,6 +938,12 @@ SELECT DISTINCT ON (location) location, time, report
|
|||||||
will normally contain additional expression(s) that determine the
|
will normally contain additional expression(s) that determine the
|
||||||
desired precedence of rows within each <literal>DISTINCT ON</> group.
|
desired precedence of rows within each <literal>DISTINCT ON</> group.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
Currently, <literal>FOR NO KEY UPDATE</>, <literal>FOR UPDATE</>,
|
||||||
|
<literal>FOR SHARE</> and <literal>FOR KEY SHARE</> cannot be
|
||||||
|
specified with <literal>DISTINCT</literal>.
|
||||||
|
</para>
|
||||||
</refsect2>
|
</refsect2>
|
||||||
|
|
||||||
<refsect2 id="SQL-UNION">
|
<refsect2 id="SQL-UNION">
|
||||||
|
Loading…
x
Reference in New Issue
Block a user