Orm: DDC-2213: Paginator does not work with composite primary key entity
Jira issue originally created by user thestanislav:
Paginator does not work with composed primary key.
"Single id is not allowed on composite primary key in entity" exception is thrown here
https://github.com/doctrine/doctrine2/blob/master/lib/Doctrine/ORM/Tools/Pagination/WhereInWalker.php#L90
Only first column values are fetched while retrieving primary keys here
https://github.com/doctrine/doctrine2/blob/master/lib/Doctrine/ORM/Tools/Pagination/Paginator.php#L173
doctrinebot
All 2 comments
Comment created by @ocramius:
Limitation was confused by issue reporter and considered bug
doctrinebot
on 23 Jan 2013
Comment created by austinsmorris:
I'd like to add some additional information because the title and description are misleading.
Paginator _does_ work with composite primary key entities. You just cannot use the Paginator when your query does a fetch join with a collection (a one-to-many or many-to-many association). See the documentation for a brief description:
[http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/tutorials/pagination.html]
In order to use Paginator with a composite primary key entity, you need to instantiate the Paginator with the $fetchJoinCollection flag set to false (it defaults to true). Now, pagination will skip the WhereInWalker which throws an exception when using a composite primary key. Fetch joins with entities (one-to-one or many-to-one) will still work. You can even use a regular join with a collection.
The only "problem" is when your Paginator query calls for a fetch join to a collection. The work around for this is to use a regular join as mentioned above. The drawback is that your paginated entities will not be hydrated with the collection. The collection will have to be lazy-loaded when called upon.
doctrinebot
on 15 Aug 2013
Related issues
doctrinebot
路
4Comments
doctrinebot
路
4Comments
doctrinebot
路
4Comments
delboy1978uk
路
3Comments
podorozhny
路
4Comments
Most helpful comment
Comment created by austinsmorris:
I'd like to add some additional information because the title and description are misleading.
Paginator _does_ work with composite primary key entities. You just cannot use the Paginator when your query does a fetch join with a collection (a one-to-many or many-to-many association). See the documentation for a brief description:
[http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/tutorials/pagination.html]
In order to use Paginator with a composite primary key entity, you need to instantiate the Paginator with the $fetchJoinCollection flag set to false (it defaults to true). Now, pagination will skip the WhereInWalker which throws an exception when using a composite primary key. Fetch joins with entities (one-to-one or many-to-one) will still work. You can even use a regular join with a collection.
The only "problem" is when your Paginator query calls for a fetch join to a collection. The work around for this is to use a regular join as mentioned above. The drawback is that your paginated entities will not be hydrated with the collection. The collection will have to be lazy-loaded when called upon.