Added missing fields to the api documentation
This commit is contained in:
parent
8105bfd8b3
commit
89c44cd14e
@ -38,39 +38,24 @@ Fields
|
|||||||
======
|
======
|
||||||
|
|
||||||
.. autoclass:: mongoengine.StringField
|
.. autoclass:: mongoengine.StringField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.URLField
|
.. autoclass:: mongoengine.URLField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.EmailField
|
.. autoclass:: mongoengine.EmailField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.IntField
|
.. autoclass:: mongoengine.IntField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.FloatField
|
.. autoclass:: mongoengine.FloatField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.DecimalField
|
.. autoclass:: mongoengine.DecimalField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.BooleanField
|
|
||||||
|
|
||||||
.. autoclass:: mongoengine.DateTimeField
|
.. autoclass:: mongoengine.DateTimeField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.ComplexDateTimeField
|
.. autoclass:: mongoengine.ComplexDateTimeField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.EmbeddedDocumentField
|
|
||||||
|
|
||||||
.. autoclass:: mongoengine.DictField
|
|
||||||
|
|
||||||
.. autoclass:: mongoengine.ListField
|
.. autoclass:: mongoengine.ListField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.SortedListField
|
.. autoclass:: mongoengine.SortedListField
|
||||||
|
.. autoclass:: mongoengine.DictField
|
||||||
.. autoclass:: mongoengine.BinaryField
|
.. autoclass:: mongoengine.MapField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.ObjectIdField
|
.. autoclass:: mongoengine.ObjectIdField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.ReferenceField
|
.. autoclass:: mongoengine.ReferenceField
|
||||||
|
|
||||||
.. autoclass:: mongoengine.GenericReferenceField
|
.. autoclass:: mongoengine.GenericReferenceField
|
||||||
|
.. autoclass:: mongoengine.EmbeddedDocumentField
|
||||||
|
.. autoclass:: mongoengine.GenericEmbeddedDocumentField
|
||||||
|
.. autoclass:: mongoengine.BooleanField
|
||||||
.. autoclass:: mongoengine.FileField
|
.. autoclass:: mongoengine.FileField
|
||||||
|
.. autoclass:: mongoengine.BinaryField
|
||||||
.. autoclass:: mongoengine.GeoPointField
|
.. autoclass:: mongoengine.GeoPointField
|
||||||
|
.. autoclass:: mongoengine.SequenceField
|
||||||
|
@ -920,9 +920,11 @@ class GeoPointField(BaseField):
|
|||||||
|
|
||||||
|
|
||||||
class SequenceField(IntField):
|
class SequenceField(IntField):
|
||||||
"""Provides a sequental counter.
|
"""Provides a sequental counter (see http://www.mongodb.org/display/DOCS/Object+IDs#ObjectIDs-SequenceNumbers)
|
||||||
|
|
||||||
..note:: Although traditional databases often use increasing sequence
|
.. note::
|
||||||
|
|
||||||
|
Although traditional databases often use increasing sequence
|
||||||
numbers for primary keys. In MongoDB, the preferred approach is to
|
numbers for primary keys. In MongoDB, the preferred approach is to
|
||||||
use Object IDs instead. The concept is that in a very large
|
use Object IDs instead. The concept is that in a very large
|
||||||
cluster of machines, it is easier to create an object ID than have
|
cluster of machines, it is easier to create an object ID than have
|
||||||
|
Loading…
x
Reference in New Issue
Block a user