0 warning As the documentation says, ORDER BY or GROUP BY destroy the depth-first hierarchical ordering of the results:
2 If you want to guarantee ordering (and you should), you can use [with ordinality](https://www.postgresql.org/docs/12/queries-table-expressions.html#QUERIES-TABLEFUNCTIONS) since version 9.4, along with an aggregate with [order by](https://www.postgresql.org/docs/12/sql-expressions.html#SYNTAX-AGGREGATES):
2 Yes, but stars are only allowed from people who can multi-star (they can still award any number of stars).
Why does adding a TOP allow the SQL Server query optimizer to find a plan that can honor a FORCESEEK hint?
13 Although the query text contains an `APPLY`, the optimizer rewrites this to a regular join using the `ApplyHandler` rule early in the compilation process (during simplification). The optimizer prefers joins over applies because it has more transformations for joins[^1](For background on the difference between join and apply, see my article [Apply versus Nested Loops Join](https://www.sql.kiwi/2019/06/apply-versus-nested-loops-join.html)).
2 `feature-request` `declined` add an 'Update this post' button on embedded db<>fiddles on TopAnswers