Merge pull request #2489 from bagerard/fix_one_to_many_doc

Fix one-to-many example that is actually a many to many
This commit is contained in:
Bastien Gérard 2021-03-09 13:41:03 +01:00 committed by GitHub
commit 1669f0c5a4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions

View File

@ -290,12 +290,12 @@ as the constructor's argument::
content = StringField() content = StringField()
.. _one-to-many-with-listfields: .. _many-to-many-with-listfields:
One to Many with ListFields Many to Many with ListFields
''''''''''''''''''''''''''' '''''''''''''''''''''''''''
If you are implementing a one to many relationship via a list of references, If you are implementing a many to many relationship via a list of references,
then the references are stored as DBRefs and to query you need to pass an then the references are stored as DBRefs and to query you need to pass an
instance of the object to the query:: instance of the object to the query::

View File

@ -915,7 +915,7 @@ class ListField(ComplexBaseField):
"""A list field that wraps a standard field, allowing multiple instances """A list field that wraps a standard field, allowing multiple instances
of the field to be used as a list in the database. of the field to be used as a list in the database.
If using with ReferenceFields see: :ref:`one-to-many-with-listfields` If using with ReferenceFields see: :ref:`many-to-many-with-listfields`
.. note:: .. note::
Required means it cannot be empty - as the default for ListFields is [] Required means it cannot be empty - as the default for ListFields is []