#26842: SQLite3 backend raises error when reading tz-aware datetime value
-------------------------------------+-------------------------------------
     Reporter:  ryochiji             |                    Owner:
                                     |  kennethyang404
         Type:  Uncategorized        |                   Status:  closed
    Component:  Database layer       |                  Version:  1.9
  (models, ORM)                      |
     Severity:  Normal               |               Resolution:  invalid
     Keywords:                       |             Triage Stage:
                                     |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by ryochiji):

 I have a bit of code (a unit test) that works in Django 1.7 and 1.8, but
 breaks in 1.9. Both 1.7 and 1.8 check the value to see if it's tz-naive
 
([https://github.com/django/django/blob/stable/1.7.x/django/db/backends/sqlite3/base.py#L52
 here] and
 
[https://github.com/django/django/blob/stable/1.8.x/django/db/backends/sqlite3/utils.py#L9
 here]) but not 1.9. Am I to interpret that this change in behavior is by
 design?

--
Ticket URL: <https://code.djangoproject.com/ticket/26842#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.4c16f76ff2d924d246fb84f64b3629d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to