1-33

Symfony2 – Franz Jordán 2011
Be careful that your class name and properties aren't mapped to a protected SQL keyword (such
as group or user). For example, if your entity class name is Group, then, by default, your table
name will be group, which will cause an SQL error in some engines. See Doctrine's Reserved SQL
keywords documentation on how to properly escape these names.
When using another library or program (ie. Doxygen) that uses annotations, you should place
the @IgnoreAnnotation annotation on the class to indicate which annotations Symfony should
ignore.
For example, to prevent the @fn annotation from throwing an exception, add the following:
/**
* @IgnoreAnnotation("fn")
*/
class Product
Generating Getters and Setters
Even though Doctrine now knows how to persist a Product object to the database, the class
itself isn't really useful yet. Since Product is just a regular PHP class, you need to create getter
and setter methods (e.g. getName(), setName()) in order to access its properties (since the
properties areprotected). Fortunately, Doctrine can do this for you by running:
php app/console doctrine:generate:entities Acme/StoreBundle/Entity/Product
This command makes sure that all of the getters and setters are generated for
the Product class. This is a safe command - you can run it over and over again: it only
generates getters and setters that don't exist (i.e. it doesn't replace your existing methods).
The doctrine:generate:entities command saves a backup of the
originalProduct.php named Product.php~. In some cases, the presence of this file can cause a
"Cannot redeclare class" error. It can be safely removed.
You can also generate all known entities (i.e. any PHP class with Doctrine mapping information)
of a bundle or an entire namespace:
php app/console doctrine:generate:entities AcmeStoreBundle
php app/console doctrine:generate:entities Acme
Doctrine doesn't care whether your properties are protected or private, or whether or not you
have a getter or setter function for a property. The getters and setters are generated here only
because you'll need them to interact with your PHP object.
Creating the Database Tables/Schema
You now have a usable Product class with mapping information so that Doctrine knows exactly
how to persist it. Of course, you don't yet have the corresponding product table in your
database. Fortunately, Doctrine can automatically create all the database tables needed for every
known entity in your application. To do this, run:
php app/console doctrine:schema:update --force
Actually, this command is incredibly powerful. It compares what your databaseshould look like
(based on the mapping information of your entities) with how itactually looks, and generates the
SQL statements needed to update the database to where it should be. In other words, if you add
86