Skip to content

Update limitations for 5.1.0b3 release #32

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.

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

Merged
merged 1 commit into from
May 8, 2025
Merged
Changes from all 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
24 changes: 18 additions & 6 deletions source/limitations-upcoming.txt
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,7 @@ types of unsupported {+framework+} and MongoDB features:
- :ref:`django-limitations-query`
- :ref:`django-limitations-management`
- :ref:`django-limitations-migration`
- :ref:`django-limitations-caching`
- :ref:`django-limitations-performance`

.. _django-limitations-transactions:
Expand Down Expand Up @@ -131,8 +132,6 @@ Querying Limitations

{+django-odm+} does not support the following ``QuerySet`` API methods:

- ``dates()``
- ``datetimes()``
- ``prefetch_related()``
- ``extra()``

Expand Down Expand Up @@ -171,8 +170,10 @@ Database Functions
- ``SHA1``, ``SHA224``, ``SHA256``, ``SHA384``, ``SHA512``
- ``Sign``

The ``tzinfo`` parameter of the ``Trunc`` database functions doesn't work
properly because MongoDB converts the result back to UTC.
- The ``tzinfo`` parameter of the
:py:class:`~django.db.models.functions.TruncDate` and
:py:class:`~django.db.models.functions.TruncTime` database functions isn't
supported.

.. _django-limitations-management:

Expand All @@ -181,7 +182,7 @@ Unsupported Management Commands

The following ``django-admin`` commands are unsupported:

- ``createcachetable``
- ``createcachetable`` (see :ref:`django-limitations-caching`)
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Looking at the rendered docs, there appears to be a docs platform bug where the closing parenthesis is included in the link. Could you report it?

Copy link
Collaborator

@norareidy norareidy May 8, 2025

Choose a reason for hiding this comment

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

interesting, I will let the platform team know. You might be able to get around it if you use :ref:Caching <django-limitations-caching>

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I don't think it matters enough to try a workaround. I'll trust the bug will be fixed soon enough. Thanks!

- ``inspectdb``

.. _django-limitations-migration:
Expand All @@ -198,6 +199,18 @@ Migration Limitations
- `DDL Transactions <{+django-docs+}/topics/migrations/#transactions>`__.
- The ``migrate --fake-initial`` option.

.. _django-limitations-caching:

Caching
~~~~~~~

Database caching uses {+django-odm+}'s ``createcachecollection`` command
rather than {+framework+}'s SQL-specific ``createcachetable`` command.

Secondly, you must use the ``django_mongodb_backend.cache.MongoDBCache``
backend rather than {+framework+}'s built-in database cache backend,
``django.core.cache.backends.db.DatabaseCache``.

.. _django-limitations-performance:

Performance
Expand Down Expand Up @@ -234,7 +247,6 @@ We plan to support the following MongoDB features in the GA release:
by using the Django API
- Queryable Encryption and Client-side Field Level Encryption
- Database transactions
- Storage of cached data in the database

We plan to support the following MongoDB features in future post-GA releases:

Expand Down
Loading