David Grudl

> But the queries you have in the tests do not pass to MSSQL. "SELECT 1 OFFSET 10 ROWS FETCH NEXT 10 ROWS ONLY" ends with MSSQL error. So tests...

There is a older attempt to implement it #293

I think that fetchAssoc is not suitable for entities. Better way is to create new `fetchEntities()` function. (It does not necessarily have to be a method of the Result class...

The solution would be to modify fetchAssoc to - not use `$this->fetch()` directly, but fetch row data via `$this->getResultDriver()->fetch(true);` - do all tranformations - apply `$this->rowFactory` & `rowClass` to the...

WIP 6b342624d71a471f4d4514d3e6683b681913addc

In fact, it is BC break :-/ See #284 In my opinion, this cannot be solved without BC. And I don't really want to deal with it :-)

Yes, I'm afraid any change can be a BC break. New interface seems like a ways how to solve. I have to think about it more and unfortunately I don't...

This would require change the limit() behavior in the Fluent, which would cause a BC break, so I don't want to deal with it at all…

I don't understand what you mean.

This is the planned feature for the next version of Dibi. (At the time Dibi was created, ten years ago, there was no measurable performing difference between a reusable query...