Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct and copyedit limitations page #20

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
+8 −43
Draft

Correct and copyedit limitations page #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
51 changes: 8 additions & 43 deletions source/limitations-upcoming.txt
View file
Open in desktop
Copy link
Collaborator

@Jibola Jibola Feb 12, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

On line 28 & 29 of this file, we reference the Drivers Feedback Forum. Let's remove that link because we should have the Github Issues & JIRA tickets be our primary proxies for tracking requests and changes.

So we should redirect folks to the Issues & Help section of the docs here instead.

cc: @R-shubham @norareidy

Original file line number Diff line number Diff line change
Expand Up @@ -39,21 +39,18 @@ types of unsupported {+framework+} and MongoDB features:
- :ref:`django-limitations-query`
- :ref:`django-limitations-management`
- :ref:`django-limitations-migration`
- :ref:`django-limitations-async`
- :ref:`django-limitations-data`
- :ref:`django-limitations-performance`

.. _django-limitations-database:

Unsupported Database Variables
Unsupported Database settings
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The following database variables are not supported by {+django-odm+}:
The following database settings are not supported by {+django-odm+}:

- ``ATOMIC_REQUESTS``
- ``AUTOCOMMIT``
- ``CONN_HEALTH_CHECKS``
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Not applicable to this backend. pymongo takes care of this functionality.

- ``TIME_ZONE``
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It works

Copy link
Collaborator

Choose a reason for hiding this comment

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

It does? Is it already converting between UTC <--> TZ when retrieved from the DB?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, see how DatabaseOperations.convert_datetimefield_value() and DatabaseOperations.convert_datetimefield_value() make use of self.connection.timezone.


.. _django-limitations-models:

Expand Down Expand Up @@ -126,7 +123,7 @@ Fields
``$lookup`` operations, see the :atlas:`Reduce $lookup Operations
</schema-suggestions/reduce-lookup-operations/>` guide in the Atlas
documentation.
- Performance of `CASCADE deletes <{+django-docs+}/ref/models/fields/#django.db.models.CASCADE>`__
- Performance of `CASCADE deletes <{+django-docs+}/ref/models/fields/#django.db.models.CASCADE>`__
on a ``ForeignKey`` field is not as performant as using an
``EmbeddedModelField``.

Expand Down Expand Up @@ -199,9 +196,6 @@ Django Management Command Limitations

- ``createcachetable``
- ``inspectdb``
- ``optimizemigration``
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It works (no db interaction).

- ``sqlflush``
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

not applicable

- ``sqlsequencereset``
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Not applicable. This backend does not support fields with sequences (AutoField).


.. _django-limitations-migration:

Expand All @@ -214,15 +208,7 @@ Migration Limitations
{+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.

.. _django-limitations-async:

Asynchronous Limitations
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It works as per mongodb/django-mongodb-backend#252.

~~~~~~~~~~~~~~~~~~~~~~~~

{+django-odm+} has not been tested for support of the asynchronous functionality of
the Django API.
- {+django-odm+} does not support the ``migrate --fake-initial`` option.

.. _django-limitations-data:

Expand All @@ -248,15 +234,13 @@ General Availability Release Features
-------------------------------------

In this section, you can learn about the following
types of {+framework+} and MongoDB features that
types of {+framework+} and MongoDB features that
GA and post-GA {+django-odm+} releases will likely introduce:

- :ref:`django-upcoming-mongodb`
- :ref:`django-upcoming-models`
- :ref:`django-upcoming-management`
- :ref:`django-upcoming-third-party`
- :ref:`django-upcoming-variables`
- :ref:`django-upcoming-async`

.. _django-upcoming-mongodb:

Expand Down Expand Up @@ -330,33 +314,14 @@ the GA release:

.. _django-upcoming-third-party:

Third Party Features
~~~~~~~~~~~~~~~~~~~~
Third Party Libraries
~~~~~~~~~~~~~~~~~~~~~

We plan to support the following third-party features in
We plan to support the following third-party libraries in
the GA release:

- `Django-filter <https://django-filter.readthedocs.io/en/stable/>`__
- `Django Rest Framework <https://www.django-rest-framework.org/>`__
- `Django-allauth <https://docs.allauth.org/en/latest/>`__
- `Wagtail <https://wagtail.org/>`__
- `Django Debug Toolbar <https://django-debug-toolbar.readthedocs.io/en/latest/>`__

.. _django-upcoming-variables:

Database Variable Support
~~~~~~~~~~~~~~~~~~~~~~~~~

We plan to support the following Django variables for configuring
your database connection in future post-GA releases:

- ``CONN_HEALTH_CHECKS``
- ``TIME_ZONE``

.. _django-upcoming-async:

Asynchronous Support
~~~~~~~~~~~~~~~~~~~~

We plan to offer asynchronous support for {+django-odm+} in
future post-GA releases.
Loading