Andrej Rypo

Since it is backwards compatible, I see no reason not to include it in v4. It can be the default in v5.

👉 PR #393 is open for v4 branch.

That PR solves a **different** issue.\ And since the PR(s) mentioned are over 3 years old, I'm not expecting them merged any time soon. This **PR does not introduce BC...

This issue most probably plagues the `Result::fetchPairs` method as well, since `property_exists` is used there too.

I was wondering if I could come up with my own solution to the problem, however, as many times before, I hit the wall called "private" or "final". First, I...

Consider this case. Really simple and useful. I want to fetch users and then have them automatically sorted into groups by company and account type. Somewhere in the database layer...

I forgot to point out that the the suggested `fetchEntities` function would have to know the depth of nesting of the result, which it does not know. And I consider...

So bascally you modify the order to do the transformations first, then apply the row factory. Well at a point in time I found it strange that the row factory...

I wonder ... it's quite common to have an entity class put all the "row data" into one attribute and use magic accessors. So you had the very same idea...

Is it not an issue that should be fixed in distribution files?