Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit0c07271

Browse files
javiereguiluzxabbuh
authored andcommitted
Removed the proposed note and updated the title
1 parent21733af commit0c07271

File tree

1 file changed

+2
-7
lines changed

1 file changed

+2
-7
lines changed

‎doctrine.rst‎

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
..index::
22
single: Doctrine
33

4-
Databases and Doctrine
5-
======================
4+
Databases andtheDoctrine ORM
5+
==============================
66

77
One of the most common and challenging tasks for any application
88
involves persisting and reading information to and from a database. Although
@@ -337,11 +337,6 @@ directly inside the ``Product`` class via DocBlock annotations:
337337
not possible to mix YAML metadata definitions with annotated PHP entity
338338
class definitions.
339339

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-
345340
..tip::
346341

347342
The table name is optional and if omitted, will be determined automatically

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp