Adding support for different fetch mode

[creativej]

In preparation for
https://github.com/99designs/contests/pull/1175

[lox]

Not overly keen on this, fetch mode should always be associative arrays. Why not just use array_values on the result if you want an ordinal array?

[lox]

Ping @creativej

[creativej]

Sorry @lox missed the ping! The problem with associative arrays is that it only holds fields with a unique names. This will cause problem for joins.

I am not sure if array_values can work here, I will double check!

[lox]

Yeah, fair point. This requires some thought.

[lox]

Ping @rbone and @mtibben:

What do you guys think? How should we support results with duplicate columns?

[rbone]

Still undecided on this one. The intent behind this is to enable joins to return unambiguous values for each domain object relevant to them e.g. if I select a series of posts, and I also want to select all the users to those posts, I want to ensure any common fields that might be present such as timecreated are maintained.

So the question I have is, does Pheasant already have an answer in mind for this use case? If it does then I'd probably shy away from a change like this to try and avoid unnecessary complexity.

[rbone]

Closing this as I don't believe it is likely to advance any further. If I'm wrong feel free to reopen it again.