QueryObject should work with native queries but it does not about doctrine HOT 15 CLOSED

Can Paginator handle NativeQuery?

from doctrine.

It does not. Lets look at ResultSet which accepts AbstractQuery in constructor. I think it is just typo in your code. However there can be some easier QueryObject which could implements subset of current methods. Don`t you think?

from doctrine.

The whole point of result set is to paginate the result, and if you pass me a native query, I have no idea ho to count the total number of rows it will return.

from doctrine.

Sadly, I failed as well to use QueryObjects for native queries.

from doctrine.

Well, ok. However there could be at least interface/abstract class which I can extend and then use it in similar way as QueryObject. Current QueryObject can use this class as well. I want to call

$result = $dao->fetch(new AwesomeNativeQuery());

The result can be then an array. The other way is to add another method to EntityDao (eg. fetchNative).

from doctrine.

Fuck, bad button.

from doctrine.

This dould be doable, if there would be optional method countNativeQuery in the query object, that you would have to implement to bypass the total count problem.

from doctrine.

Total count by subselect would not be a problem.

from doctrine.

Are you sure that is a good idea?

from doctrine.

Well, not universally, since sometimes you have 1:N joins. :|

from doctrine.

I agree with @Majkl578 - Doctrine do it itself in Paginator.

from doctrine.

Would you guys give it a try please?

from doctrine.

It shouldn't be closed, right?

from doctrine.

Well, I've tested it and it worked, so why not?

from doctrine.

I thought it is in some pull request at first. I must agree now :-)

from doctrine.