Unexpected "order by (SELECT NULL)" when setting a limit
return session()->find<Model::Falukant::Predefine::FirstName>() .where("\"name\" = ?") .bind(tr) .limit(1);
select "id", "version", "name" from "FALUKANT_PREDEFINE"."firstname" where ("name" = ?) order by (select null) offset 0 rows fetch first (?) rows only
I don't expect an "order by" when I don't add it.
Without the limit(1), the "order by..." is also not set.
Updated by Torsten Schulz 3 months ago
Korneel Dumon wrote in #note-1:
I think one of the back-ends requires it. Does it cause problems for you?
I really had problems with it, because without print the SQL, I wouldn't know about that. I spend a lot of time into find the reason of an query that was working in cli wasn't working in Wt DBO.