Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions source/get-started.txt
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
.. _django-get-started:

===============================
=======================================
Get Started with {+django-odm+}
===============================
=======================================

.. contents:: On this page
:local:
Expand Down
33 changes: 15 additions & 18 deletions source/limitations-upcoming.txt
Original file line number Diff line number Diff line change
Expand Up @@ -75,10 +75,6 @@ Indexes
- Creating geospatial indexes through the Django Indexes API
- Updating indexes in ``EmbeddedModelFields`` after model creation

To learn how to run unsupported database operations by operating directly on
your ``MongoClient`` instance, see :ref:`django-client-operations` in the
Perform Raw Database Queries guide.

.. _django-limitations-models-fields:

Fields
Expand All @@ -88,15 +84,15 @@ Fields

- ``ArrayField``

- {+django-odm+} does not support ``ArrayField`` polymorphism.
- {+django-odm+} does not support nesting an ``EmbeddedModelField`` within an ``ArrayField``.
- ``ArrayField`` polymorphism is not supported.
- Nested ``EmbeddedModelField`` values within an ``ArrayField`` is not supported.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Nested ``EmbeddedModelField`` values within an ``ArrayField`` is not supported.
- Nested ``EmbeddedModelField`` values within an ``ArrayField`` are not supported.


- ``EmbeddedModelField``

- ``EmbeddedModel`` schema changes do not register after creation.
- Embedded documents cannot take Django foreign keys.
- {+django-odm+} does not support arbitrary or untyped embedded model
fields. You must derive all fields from a ``EmbeddedModel`` class.
- Arbitrary or untyped embedded model fields are not supported. You must
derive all fields from a ``EmbeddedModel`` class.

- ``JSONField``

Expand All @@ -110,8 +106,7 @@ Fields

- ``DateTimeField``

- {+django-odm+} does not support microsecond granularity for
``DateTimeField``.
- Microsecond granularity for ``DateTimeField`` values is not supported.

- ``DurationField``

Expand Down Expand Up @@ -156,9 +151,10 @@ that span multiple collections.
Geospatial Queries
``````````````````

- {+django-odm+} does not support ``GeoDjango``.
- {+django-odm+} does not have any Django lookup operators for MongoDB-specific
geospatial queries.
{+django-odm+} does not support the following geospatial query features:

- ``GeoDjango``
- Django lookup operators for MongoDB-specific geospatial queries

Aggregation Operators
`````````````````````
Expand Down Expand Up @@ -208,13 +204,14 @@ Django Management Command Limitations
Migration Limitations
~~~~~~~~~~~~~~~~~~~~~

- {+django-odm+} does not support enforced schema validation. To learn how to
enforce schema validation in your application, see the :manual:`Specify JSON
{+django-odm+} does not support the following migration features:

- Enforced schema validation. To learn how to enforce schema
validation in your application, see the :manual:`Specify JSON
Schema Validation </core/schema-validation/specify-json-schema/>` guide in the
{+mdb-server+} manual.
- {+django-odm+} does not support `DDL Transactions
<{+django-docs+}/topics/migrations/#transactions>`__.
- {+django-odm+} does not support the ``migrate --fake-initial`` command.
- `DDL Transactions <{+django-docs+}/topics/migrations/#transactions>`__.
- ``migrate --fake-initial`` command.

.. _django-limitations-async:

Expand Down
Loading