1-33

Symfony2 – Franz Jordán 2011
When you query for a particular type of object, you always use what's known as its "repository".
You can think of a repository as a PHP class whose only job is to help you fetch entities of a
certain class. You can access the repository object for an entity class via:
$repository = $this->getDoctrine()
->getRepository('AcmeStoreBundle:Product');
The AcmeStoreBundle:Product string is a shortcut you can use anywhere in Doctrine instead
of the full class name of the entity (i.e.Acme\StoreBundle\Entity\Product). As long as your
entity lives under the Entitynamespace of your bundle, this will work.
Once you have your repository, you have access to all sorts of helpful methods:
// query by the primary key (usually "id")
$product = $repository->find($id);
// dynamic method names to find based on a column value
$product = $repository->findOneById($id);
$product = $repository->findOneByName('foo');
// find *all* products
$products = $repository->findAll();
// find a group of products based on an arbitrary column value
$products = $repository->findByPrice(19.99);
Of course, you can also issue complex queries, which you'll learn more about in theQuerying for
Objects section.
You can also take advantage of the useful findBy and findOneBy methods to easily fetch
objects based on multiple conditions:
// query for one product matching be name and price
$product = $repository->findOneBy(array('name' => 'foo', 'price' => 19.99));
// query for all products matching the name, ordered by price
$product = $repository->findBy(
array('name' => 'foo'),
array('price' => 'ASC')
);
When you render any page, you can see how many queries were made in the bottom right corner
of the web debug toolbar.
89