Closed
Description
As this code in FetchableFluentQueryBySpecification
shows, adding a limit
applies the current sorting again.
In my application, this is causing duplicate order by
clause to be included in the SQL generated like order by q1_0."id" desc,q1_0."id" desc
, as I call .sortBy
first, and then .limit
.
Of course, it's easy to fix on the application's side by calling .limit
first, but I think this is a bug in the framework, as the other class FetchableFluentQueryByPredicate
implementing the same interface does not have this behavior.