Hello, We've finally thought of a workaround for this SQL Server limitation. We'll simply render
ORDER BY @@version The @@version variable is evaluated quickly and does not impair / influence the execution plan. At the same time, SQL Server's strict ORDER / OFFSET / FETCH semantics is maintained correctly. As a matter of fact, this might help work around a couple of limitations to window functions as well, where ORDER BY clauses are mandatory. The fix will be included in jOOQ 3.4.0, 3.3.3, 3.2.6 Best Regards, Lukas -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
