#23631: Documentation: Outdated warning about DateTimeField on MySQL?
-------------------------------+------------------------------------
     Reporter:  marfire        |                    Owner:  nobody
         Type:  Bug            |                   Status:  new
    Component:  Documentation  |                  Version:  master
     Severity:  Normal         |               Resolution:
     Keywords:                 |             Triage Stage:  Accepted
    Has patch:  1              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+------------------------------------

Comment (by marfire):

 I think that wording is a little confusing if you're not already familiar
 with the way timezone-handling works. I would say something like this:

 > MySQL does not have a timezone-aware column type. When `USE_TZ = True`
 and an attempt is made to store a timezone-aware `datetime` (or `time`) in
 a `DateTimeField` (or `TimeField`), the datetime is converted to UTC and
 stored without a timezone. When `USE_TZ = False`, though, Django chooses
 to raise a `ValueError` rather than simply discard the timezone
 information in the aware datetime.

 Either way, though, you should include the same warning for Oracle and
 SQLite, since they display the same behavior (see
 
[https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L508-512
 here] and
 
[https://github.com/django/django/blob/master/django/db/backends/sqlite3/base.py#L249-253
 here]).

 (Sorry, I'm not able to create an actual patch at the moment.)

--
Ticket URL: <https://code.djangoproject.com/ticket/23631#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.4147835802b852da56ddb74dd5903ce6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to