Change simple references to ID references

doctrine · Dec 19, 2017 · c0c0d0d · c0c0d0d
1 parent 5aa958a
commit c0c0d0d
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 13 deletions.
diff --git a/docs/en/reference/annotations-reference.rst b/docs/en/reference/annotations-reference.rst
@@ -929,8 +929,6 @@ Optional attributes:
 -
     targetDocument - A |FQCN| of the target document. A ``targetDocument`` is
     required when using ``storeAs: id``.
--
-    simple - deprecated (use ``storeAs: id``)
 -
     storeAs - Indicates how to store the reference. ``id`` stores the identifier,
     ``ref`` an embedded object containing the ``id`` field and (optionally) a
@@ -1005,8 +1003,6 @@ Optional attributes:
 -
     targetDocument - A |FQCN| of the target document. A ``targetDocument`` is
     required when using ``storeAs: id``.
--
-    simple - deprecated (use ``storeAs: id``)
 -
     storeAs - Indicates how to store the reference. ``id`` stores the identifier,
     ``ref`` an embedded object containing the ``id`` field and (optionally) a

diff --git a/docs/en/reference/priming-references.rst b/docs/en/reference/priming-references.rst
@@ -83,7 +83,7 @@ queries (one per discriminated class name).
 
 .. note::
 
-    Priming is also compatible with :ref:`simple references <storing_references>`
+    Priming is also compatible with :ref:`ID references <storing_references>`
     and discriminated references. When priming discriminated references, ODM
     will issue one query per distinct class among the referenced document(s).
 

diff --git a/docs/en/reference/reference-mapping.rst b/docs/en/reference/reference-mapping.rst
@@ -317,7 +317,7 @@ Storing References
 By default all references are stored as a `DBRef`_ object with the traditional
 ``$ref``, ``$id``, and (optionally) ``$db`` fields (in that order). For references to
 documents of a single collection, storing the collection (and database) names for
-each reference may be redundant. You can use simple references to store the
+each reference may be redundant. You can use ID references to store the
 referenced document's identifier (e.g. ``MongoId``) instead of a `DBRef`_.
 
 Example:
@@ -346,8 +346,8 @@ Example:
 Now, the ``profile`` field will only store the ``MongoId`` of the referenced
 Profile document.
 
-Simple references reduce the amount of storage used, both for the document
-itself and any indexes on the reference field; however, simple references cannot
+ID references reduce the amount of storage used, both for the document
+itself and any indexes on the reference field; however, ID references cannot
 be used with discriminators, since there is no `DBRef`_ object in which to store
 a discriminator value.
 
@@ -363,11 +363,6 @@ The ``storeAs`` option has the following possible values:
 - **ref**: Uses a custom embedded object with an ``id`` field
 - **id**: Uses the identifier of the referenced object
 
-.. note::
-
-    The ``storeAs=id`` option used to be called a "simple reference". The old syntax is
-    still recognized (so using ``simple=true`` will imply ``storeAs=id``).
-
 .. note::
 
     For backwards compatibility ``storeAs=dbRefWithDb`` is the default, but