Added section on by-table semantics (#1345)

Adding section on by-table semantics for NEXT, removing the section on
known limitations.

---------

Co-authored-by: Richard Sill <[email protected]>
Co-authored-by: Hannes Voigt <[email protected]>
Co-authored-by: hvub <[email protected]>
Co-authored-by: Richard Sill <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>

Author: 4 people

modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc

@@ -32,6 +32,31 @@ For more information, see xref:queries/select-version.adoc[].
 | Feature
 | Details
 
+a|
+label:functionality[]
+label:updated[]
+[source, cypher]
+----
+MATCH (p:Product) WHERE p.name <> "Coffee"
+CALL (p) {
+    MATCH (p)<-[:BUYS]-(c:Customer)-[:BUYS]->(otherProduct)
+    RETURN c, otherProduct
+    NEXT
+    RETURN count(DISTINCT c) AS customers, 0 AS customersAlsoBuyingCoffee
+    UNION
+    FILTER otherProduct.name = "Coffee"
+    RETURN 0 as customers, count(DISTINCT c) AS customersAlsoBuyingCoffee
+    NEXT
+    RETURN max(customers) AS customers, max(customersAlsoBuyingCoffee) AS customersAlsoBuyingCoffee
+}
+RETURN p.name AS product,
+       round(toFloat(customersAlsoBuyingCoffee) * 100 / customers, 1) AS percentageOfCustomersAlsoBuyingCoffee
+  ORDER BY product
+----
+
+| `NEXT` now correctly supports aggregations in the context of `UNION` and `CALL`.
+For more information, see xref:queries/composed-queries/sequential-queries.adoc#issues-fixes[Sequential queries (`NEXT`) > Known issues and fixes].
+
 a|
 label:functionality[]
 label:updated[]