#1615: Doctrine_Pager is highly inefficient
------------------------+---------------------------------------------------
Reporter: colnector | Owner: guilhermeblanco
Type: task | Status: new
Priority: major | Milestone: Unknown
Component: Pager | Version: 1.0.3
Resolution: | Keywords:
Has_test: 0 | Mystatus: Pending User Response
Has_patch: 0 |
------------------------+---------------------------------------------------
Changes (by guilhermeblanco):
* mystatus: Pending Core Response => Pending User Response
Comment:
It only issues 3 queries if you do not play with setCountQuery. Most
queries can be optimized into a single select.
There're only a few situations were 3 queries must be applied and we
cannot control it.
So if you need more help, please give me your models, query and a
description of what do you want to retrieve.
Pager is not inefficient, it only adds the limit/offset restriction. If
you want to consider anything inefficient, it's the limit-subquery here.
Regards,
--
Ticket URL: <http://trac.doctrine-project.org/ticket/1615#comment:5>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"doctrine-svn" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---