1. Databases and Doctrine

2. Doctrine ORM
● aims to let you map objects to a relational
database (such as MySQL, PostgreSQL or
Microsoft SQL)

3. A Simple Example: A Product
● $ php app/console generate:bundle
--namespace=Acme/StoreBundle

4. Configuring the Database
● configure your database connection information
in an app/config/parameters.yml file

5. parameters defined in that file are
referenced by the main
configuration file:

6. Now that Doctrine knows about your
database, you can have it create the
database for you:
● $ php app/console
doctrine:database:create
Or destroy the DB:
● $ php app/console
doctrine:database:drop ­­force

7. Creating your first table...

8. Creating an Entity Class
● Create this class inside the Entity directory of
your AcmeStoreBundle:

9. Add Mapping Information
● Doctrine allows you to persist entire objects to
the database and fetch entire objects out of the
database.

11. Doctrine Field Types Reference
● Strings
● string (used for shorter strings)
● text (used for larger strings)
● Numbers
● integer
● smallint
● bigint
● decimal
● float
● Dates and Times (use a DateTime object for these fields in PHP)
● date
● time
● datetime
● Other Types
● boolean
● object (serialized and stored in a CLOB field)
● array (serialized and stored in a CLOB field)
http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/basic-
mapping.html#doctrine-mapping-types

12. Generating Getters and Setters
● $ php app/console
doctrine:generate:entities
Acme/StoreBundle/Entity/Product

13. ● 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

14. Creating the Database
Tables/Schema
● $ php app/console
doctrine:schema:update ­­force

15. Persisting Objects to the Database

16. Fetching Objects from the Database

17. helpful methods:

18. findBy and findOneBy methods to
easily fetch objects based on
multiple conditions

19. Updating an Object

20. Deleting an Object

21. Querying for Objects

22. Querying for Objects with DQL
● The getResult() method returns an array of
results.

23. querying for just one object

24. Setting Parameters

25. Using Doctrine's Query Builder

26. Mapping Custom Repository Classes
● a custom repository class for your entity and
add methods with your query logic there.

27. Creating Custom Repository Classes

28. Using Custom Repository Classes
● When using a custom repository class, you still
have access to the default finder methods such
as find() and findAll().

29. Entity Relationships/Associations
Category
ProductProduct Product

30. Relationship Mapping Metadata

31. since each Product class can relate to exactly one
Category object
● Then, generate the setter(s) and getter(s)
●
● tell Doctrine to add the new category table, and
product.category_id column, and new foreign key:

33. Saving Related Entities

34. Fetching Related Objects

35. Lazy Loading

36. Joining to Related Records

37. Field Options

38. More on Association Mapping

39. One-To-One, Unidirectional

40. One-To-One, Bidirectional

41. One-To-One, Self-referencing

42. One-To-Many, Unidirectional with Join Table

43. Many-To-One, Unidirectional

44. One-To-Many, Bidirectional

45. One-To-Many, Self-referencing

46. Many-To-Many, Unidirectional

47. Many-To-Many, Bidirectional

48. Many-To-Many, Self-referencing

49. Mapping Defaults
● defaults for a join column in a one-to-one/many-to-one
association is as follows:
● name: "<fieldname>_id"
● referencedColumnName: "id"

51. For more info:
http://www.doctrine-project.org/