/rtmp/order.diff
text/x-diff
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: unified
| File | + | − |
|---|---|---|
| doc/src/sgml/advanced.sgml | 0 | 0 |
diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml
index 11859b4..218988e 100644
*** a/doc/src/sgml/advanced.sgml
--- b/doc/src/sgml/advanced.sgml
*************** SELECT depname, empno, salary, avg(salar
*** 383,392 ****
</para>
<para>
! Although <function>avg</> will produce the same result no matter
! what order it processes the partition's rows in, this is not true of all
! window functions. When needed, you can control that order using
! <literal>ORDER BY</> within <literal>OVER</>. Here is an example:
<programlisting>
SELECT depname, empno, salary, rank() OVER (PARTITION BY depname ORDER BY salary DESC) FROM empsalary;
--- 383,392 ----
</para>
<para>
! You can also control the order in which rows are processed by
! window functions using <literal>ORDER BY</> within <literal>OVER</>.
! (The window <literal>ORDER BY</> does not even have to match the
! order in which the rows are output.) Here is an example:
<programlisting>
SELECT depname, empno, salary, rank() OVER (PARTITION BY depname ORDER BY salary DESC) FROM empsalary;