1-33

Symfony2 – Franz Jordán 2011
public function showAction($id)
{
$product = $this->getDoctrine()
->getRepository('AcmeStoreBundle:Product')
->findOneByIdJoinedToCategory($id);
$category = $product->getCategory();
// ...
}
More Information on Associations
This section has been an introduction to one common type of entity relationship, the one-tomany
relationship. For more advanced details and examples of how to use other types of
relations (e.g.one-to-one, many-to-many), see Doctrine's Association Mapping Documentation.
If you're using annotations, you'll need to prepend all annotations
with ORM\ (e.g.ORM\OneToMany), which is not reflected in Doctrine's documentation. You'll
also need to include the use Doctrine\ORM\Mapping as ORM; statement,
which importsthe ORM annotations prefix.
Configuration
Doctrine is highly configurable, though you probably won't ever need to worry about most of its
options. To find out more about configuring Doctrine, see the Doctrine section of the reference
manual.
Lifecycle Callbacks
Sometimes, you need to perform an action right before or after an entity is inserted, updated, or
deleted. These types of actions are known as "lifecycle" callbacks, as they're callback methods
that you need to execute during different stages of the lifecycle of an entity (e.g. the entity is
inserted, updated, deleted, etc).
If you're using annotations for your metadata, start by enabling the lifecycle callbacks. This is
not necessary if you're using YAML or XML for your mapping:
/**
* @ORM\Entity()
* @ORM\HasLifecycleCallbacks()
*/
class Product
{
}
// ...
Now, you can tell Doctrine to execute a method on any of the available lifecycle events. For
example, suppose you want to set a created date column to the current date, only when the
entity is first persisted (i.e. inserted):
/**
* @ORM\prePersist
*/
public function setCreatedValue()
{
}
$this->created = new \DateTime();
99