Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#30733 closed Cleanup/optimization (fixed)

Document that datetime lookups require time zone definitions in the database.

Reported by: Andrew Williams Owned by: Andrew Williams
Component: Documentation Version: 2.2
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Andrew Williams)

In the QuerySet documentation, many of the APIs that work on datetime fields have a variation of the same notice indicating that when the USE_TZ setting is set to True, the database is used to do timezone conversions. It'd be worth replacing these with the most helpful of the variations.

Pull Request: ​https://github.com/django/django/pull/11718

Change History (4)

comment:1 by Andrew Williams, 5 years ago

Description: modified (diff)
Owner: changed from nobody to Andrew Williams
Status: new → assigned

comment:2 by Mariusz Felisiak, 5 years ago

Summary: Make datetime timezone conversion notices more consistent → Document that datetime lookups require time zone definitions in the database.
Triage Stage: Unreviewed → Accepted

comment:3 by Mariusz Felisiak <felisiak.mariusz@…>, 5 years ago

Resolution: → fixed
Status: assigned → closed

In 29adcd2:

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.

comment:4 by Mariusz Felisiak <felisiak.mariusz@…>, 5 years ago

In 16e5e8ff:

[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

Note: See TracTickets for help on using tickets.
Back to Top