DOCSP-48184: Rework limitations and upcoming #27
Conversation
✅ Deploy Preview for docs-django ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
source/limitations-upcoming.txt
Outdated
| not supported. Instead, use ``ObjectIdField``. | ||
| - *Unsupported*. | ||
|
|
||
| * - ``BSONRegExp`` |
There was a problem hiding this comment.
This is not a field but a BSON data type.
There was a problem hiding this comment.
Moved to the Mongodb "Data Type Support" section
source/limitations-upcoming.txt
Outdated
|
|
||
| Performance | ||
| ~~~~~~~~~~~ | ||
| * - ``compilemessages`` |
There was a problem hiding this comment.
It's strange to list all the management commands as many of them do not interact with the database.
There was a problem hiding this comment.
Which commands do you think are relevant to include?
There was a problem hiding this comment.
As in other sections, including only the unsupported commands is sufficient.
source/limitations-upcoming.txt
Outdated
| * - `Django-filter <https://django-filter.readthedocs.io/en/stable/>`__ | ||
| - *Unsupported*. | ||
| - ✓ |
There was a problem hiding this comment.
As far as I know, it is supported because @aclark4life didn't identify any needed changes.
There was a problem hiding this comment.
Following up with him!
source/limitations-upcoming.txt
Outdated
| * - Making migrations | ||
| - ✓ | ||
| - ✓ |
There was a problem hiding this comment.
It is strange to list "Making migrations, Recording schema history, Storing migration files". These are the basics of the migrations system, and we wouldn't have any support without them.
| - *Full Support Not Planned*. However, we plan to address the | ||
| ``Q`` object and ``None`` key filtering limitations in a post-GA release. |
There was a problem hiding this comment.
I'm not sure they can be. \cc @WaVEV
source/limitations-upcoming.txt
Outdated
| * - ``as_manager()`` | ||
| - ✓ | ||
| - ✓ |
There was a problem hiding this comment.
This isn't a method that interacts with the database. Do we need to list every supported method? You didn't list every supported model field, so there seems to be a slight inconsistency.
There was a problem hiding this comment.
Since there's already a list of all supported model fields in the Models guide, I linked out to it instead of repeating them. But I agree that this table is pretty long; I can just list the unsupported/partially supported, then link to the Django QuerySet docs and say that we support all other methods not mentioned?
source/limitations-upcoming.txt
Outdated
| * - Atlas Search and Atlas Vector Search indexes | ||
| - *Partially Supported*. You cannot use the Django | ||
| Indexes API to create these indexes, but you can use | ||
| the PyMongo Driver by :ref:`exposing your MongoClient <django-client-operations>`. |
There was a problem hiding this comment.
By this definition (partial support = can do it in pymongo), I'd think nearly everything that's unsupported would be considered partially supported.
There was a problem hiding this comment.
I changed to "Unsupported" but kept the information about exposing the MongoClient
source/limitations-upcoming.txt
Outdated
| * - ``distinct()`` | ||
| - *Unsupported*. | ||
| - *Unsupported*. |
There was a problem hiding this comment.
Correction: distinct() is supported.
|
|
||
| - ``DurationField`` | ||
| .. list-table:: |
There was a problem hiding this comment.
S: suggest adding a stub column to all tables to separate the feature name from the support columns
Pull Request Info
PR Reviewing Guidelines
JIRA - https://jira.mongodb.org/browse/DOCSP-48184
Staging Links
Self-Review Checklist