Correct and copyedit limitations page #20
Conversation
✅ Deploy Preview for docs-django ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| - ``ATOMIC_REQUESTS`` | ||
| - ``AUTOCOMMIT`` | ||
| - ``CONN_HEALTH_CHECKS`` | ||
| - ``TIME_ZONE`` |
There was a problem hiding this comment.
It does? Is it already converting between UTC <--> TZ when retrieved from the DB?
There was a problem hiding this comment.
Yes, see how DatabaseOperations.convert_datetimefield_value() and DatabaseOperations.convert_datetimefield_value() make use of self.connection.timezone.
| @@ -199,9 +198,6 @@ Django Management Command Limitations | |||
|
|
|||
| - ``createcachetable`` | |||
| - ``inspectdb`` | |||
| - ``optimizemigration`` | |||
There was a problem hiding this comment.
It works (no db interaction).
| @@ -199,9 +198,6 @@ Django Management Command Limitations | |||
|
|
|||
| - ``createcachetable`` | |||
| - ``inspectdb`` | |||
| - ``optimizemigration`` | |||
| - ``sqlflush`` | |||
| - ``sqlsequencereset`` | |||
There was a problem hiding this comment.
Not applicable. This backend does not support fields with sequences (AutoField).
| @@ -199,9 +198,6 @@ Django Management Command Limitations | |||
|
|
|||
| - ``createcachetable`` | |||
| - ``inspectdb`` | |||
| - ``optimizemigration`` | |||
| - ``sqlflush`` | |||
timgraham
force-pushed
the
correct-limitations
branch
from
ecd1427 to
c7d07dc
Compare
|
|
||
| .. _django-limitations-async: | ||
|
|
||
| Asynchronous Limitations |
There was a problem hiding this comment.
It works as per mongodb/django-mongodb-backend#252.
|
|
||
| - ``ATOMIC_REQUESTS`` | ||
| - ``AUTOCOMMIT`` | ||
| - ``CONN_HEALTH_CHECKS`` |
There was a problem hiding this comment.
Not applicable to this backend. pymongo takes care of this functionality.
There was a problem hiding this comment.
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
[work in progress]