1-33

Symfony2 – Franz Jordán 2011
The above example assumes that you've created and mapped a created property (not shown
here).
Now, right before the entity is first persisted, Doctrine will automatically call this method and
thecreated field will be set to the current date.
This can be repeated for any of the other lifecycle events, which include:
preRemove
postRemove
prePersist
postPersist
preUpdate
postUpdate
postLoad
loadClassMetadata
For more information on what these lifecycle events mean and lifecycle callbacks in general, see
Doctrine's Lifecycle Events documentation
Lifecycle Callbacks and Event Listeners
Notice that the setCreatedValue() method receives no arguments. This is always the case for
lifecylce callbacks and is intentional: lifecycle callbacks should be simple methods that are
concerned with internally transforming data in the entity (e.g. setting a created/updated field,
generating a slug value).
If you need to do some heavier lifting - like perform logging or send an email - you should
register an external class as an event listener or subscriber and give it access to whatever
resources you need. For more information, see Registering Event Listeners and Subscribers.
Doctrine Extensions: Timestampable, Sluggable, etc.
Doctrine is quite flexible, and a number of third-party extensions are available that allow you to
easily perform repeated and common tasks on your entities. These include thing such
as Sluggable,Timestampable, Loggable, Translatable, and Tree.
For more information on how to find and use these extensions, see the cookbook article
aboutusing common Doctrine extensions.
Doctrine Field Types Reference
Doctrine comes with a large number of field types available. Each of these maps a PHP data type
to a specific column type in whatever database you're using. The following types are supported
in Doctrine:
Strings
Numbers
string (used for shorter strings)
text (used for larger strings)
integer
100