Re: [Django] #30733: Document that datetime lookups require time zone definitions in the database.

[Django]

#30733: Document that datetime lookups require time zone definitions in the
database.
-+-
 Reporter:  Andrew Williams  |Owner:  Andrew
 Type:   |  Williams
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.2
 Severity:  Normal   |   Resolution:  fixed
 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 Mariusz Felisiak ):

 In [changeset:"16e5e8ff5a8c8eb5bfd5de999b22803819c6881e" 16e5e8ff]:
 {{{
 #!CommitTicketReference repository=""
 revision="16e5e8ff5a8c8eb5bfd5de999b22803819c6881e"
 [2.2.x] Fixed #30733 -- Doc'd that datetime lookups require time zone
 definitions in the database.

 Note was missing for date, year, iso_year, week, time, hour, minute,
 and second lookups.

 Backport of 29adcd215f80383f00d9f837311e857142319722 from master
 }}}

-- 
Ticket URL: 
Django 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.edf06577df05d587d5c90f0a6793e1f9%40djangoproject.com.

Re: [Django] #30733: Document that datetime lookups require time zone definitions in the database.

[Django]

#30733: Document that datetime lookups require time zone definitions in the
database.
-+-
 Reporter:  Andrew Williams  |Owner:  Andrew
 Type:   |  Williams
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  2.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"29adcd215f80383f00d9f837311e857142319722" 29adcd2]:
 {{{
 #!CommitTicketReference repository=""
 revision="29adcd215f80383f00d9f837311e857142319722"
 Fixed #30733 -- Doc'd that datetime lookups require time zone definitions
 in the database.

 Note was missing for date, year, iso_year, week, time, hour, minute,
 and second lookups.
 }}}

-- 
Ticket URL: 
Django 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f910e30f7cd1926d5357d7532d5cc66f%40djangoproject.com.

Re: [Django] #30733: Document that datetime lookups require time zone definitions in the database. (was: Make datetime timezone conversion notices more consistent)

[Django]

#30733: Document that datetime lookups require time zone definitions in the
database.
-+-
 Reporter:  Andrew Williams  |Owner:  Andrew
 Type:   |  Williams
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  2.2
 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
-+-
Changes (by felixxm):

 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.2584fa24588430a95c217dbc7ac06cd8%40djangoproject.com.