Doctrine many repository for same entity - doctrine

Question

is it possible to have two repositories for the same entity ?
I try something like that, but it does not work..
class PackageRepository extends EntityRepository
{
public function __construct($em, Mapping\ClassMetadata $class)
{
$cmf = $em->getMetadataFactory();
$class = $cmf->getMetadataFor('Product');
parent::__construct($em, $class);
}
}
Any ideas ?

Answer 1

First of all, why would you want to do that?
Second, to answer your question. You can have as many repositories working with same entities as you like, they are just simple classes after all.
But you can link only one class with the entity class using the #Repository annotation (or YAML, or XML, whatever). All the mapping data is stored in the EntityManager. EntityManager will know only one repository class is linked with the entity class, if you try to get it with $entity->getReposiotry() or similar it will return only the linked class.
But nothing can stop you from creating your own classes which do some queries and call them directly, explicitly, without relying on the EntityManagers repository mapping.

Answer 2

I also have run into the same issue, when two Symfony bundles work with same entity, but queries are different for each bundle, so I also decided create separate repository for each bundle. For Doctrine 2 the solution can be:
"#Repository annotation" can be used to point default repository or just avoid it.
Create usual repository class, e.g. "MyEntityRepository".
In code:
$myEntityRepo = new MyEntityRepository($entityManager, $entityManager->getClassMetadata('AppBundle:MyEntity'));

Answer 3

I found the solution. Something in PHP called Trait.
Example:
class UserRepository extends EntityRepository {
public function adminQuery1();
public function adminQuery2();
public function adminQuery3();
public function adminQuery4();
public function adminQuery5();
public function adminQuery6();
public function frontEndQuery1();
public function frontEndQuery2();
public function frontEndQuery3();
public function frontEndQuery4();
public function frontEndQuery5();
public function frontEndQuery6();
}
Now keep on going with different specific query portions and your repository quickly becomes confusing and too long.
You could
Create multiple repository that inherit each other OR
Use traits
Example Below:
Trait AdminQuery {
public function adminQuery1();
public function adminQuery2();
public function adminQuery3();
public function adminQuery4();
public function adminQuery5();
public function adminQuery6();
}
Trait FrontEndQuery {
public function adminQuery1();
public function adminQuery2();
public function adminQuery3();
public function adminQuery4();
public function adminQuery5();
public function adminQuery6();
}
The actual repository class.
class UserRepository extends EntityRepository {
use AdminQuery;
use FrontEndQuery;
}
The beauty of this is that the keyword this will refer to the context in which the the Trait was used meaning you have access to all functions of EntityRepository
Finally found a use case for Trait.