1-33

Symfony2 – Franz Jordán 2011
This task should only be really used during development. For a more robust method of
systematically updating your production database, read about Doctrine migrations.
Saving Related Entities
Now, let's see the code in action. Imagine you're inside a controller:
// ...
use Acme\StoreBundle\Entity\Category;
use Acme\StoreBundle\Entity\Product;
use Symfony\Component\HttpFoundation\Response;
// ...
class DefaultController extends Controller
{
public function createProductAction()
{
$category = new Category();
$category->setName('Main Products');
$product = new Product();
$product->setName('Foo');
$product->setPrice(19.99);
// relate this product to the category
$product->setCategory($category);
$em = $this->getDoctrine()->getEntityManager();
$em->persist($category);
$em->persist($product);
$em->flush();
}
}
return new Response(
);
'Created product id: '.$product->getId().' and category id: '.$category->getId()
Now, a single row is added to both the category and product tables.
The product.category_idcolumn for the new product is set to whatever the id is of the new
category. Doctrine manages the persistence of this relationship for you.
Fetching Related Objects
When you need to fetch associated objects, your workflow looks just like it did before. First,
fetch a$product object and then access its related Category:
public function showAction($id)
{
$product = $this->getDoctrine()
->getRepository('AcmeStoreBundle:Product')
->find($id);
$categoryName = $product->getCategory()->getName();
96