|
1 | 1 | ..index:: |
2 | 2 | single: Doctrine |
3 | 3 |
|
4 | | -Databases and Doctrine |
5 | | -====================== |
| 4 | +Databases andtheDoctrine ORM |
| 5 | +============================== |
6 | 6 |
|
7 | 7 | One of the most common and challenging tasks for any application |
8 | 8 | involves persisting and reading information to and from a database. Although |
@@ -337,11 +337,6 @@ directly inside the ``Product`` class via DocBlock annotations: |
337 | 337 | not possible to mix YAML metadata definitions with annotated PHP entity |
338 | 338 | class definitions. |
339 | 339 |
|
340 | | -..note:: |
341 | | - |
342 | | - If using the Doctrine ODM the mapping of the `id` field is slightly different. You should define the field as normal, under the `fields` key, and add `id: true` to the definition. See the `Doctrine MongoDB YAML Driver documentation<http://docs.doctrine-project.org/projects/doctrine-mongodb-odm/en/latest/reference/yml-mapping.html>`_ for more info. |
343 | | - Using the above format will result in the error "No identifier/primary key specified for Document '<document class>'. Every Document must have an identifier/primary key.". |
344 | | - |
345 | 340 | ..tip:: |
346 | 341 |
|
347 | 342 | The table name is optional and if omitted, will be determined automatically |
|