| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
The primary use case is to interact with a third-party database (not
primarily managed by Django) that doesn't support time zones and where
datetimes are stored in local time when USE_TZ is True.
Configuring a PostgreSQL database with the TIME_ZONE option while USE_TZ
is False used to result in silent data corruption. Now this is an error.
|
|
|
|
|
|
|
|
Thanks Pakal and Claude.
|
|
|
|
|
|
|
|
|
|
Kept support for creating models without migrations when running tests
(especially for Django's test suite).
|
|
|
|
|
|
This makes room for a more general introduction about templating.
Updated some links to point to the new location, but kept those that
didn't talk specifically about the DTL.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Refs #23677.
|
|
and YEAR_MONTH.
|
|
|
|
|
|
Thanks jamesbeith for the report.
|
|
4ad57bbe31bc1813264824111de2f9f74dbda0d6 included a few odd
quotation marks.
|
|
Thanks to Tim Graham for the review.
|
|
Thanks oinopion for the suggestion and jarus for the initial patch.
|
|
|
|
Thanks gkoller for the report.
|
|
|
|
|
|
Thanks Carl Meyer for django-secure and for reviewing.
Thanks also to Zach Borboa, Erik Romijn, Collin Anderson, and
Jorge Carleitao for reviews.
|
|
Thanks jwmayfield, serg.partizan, and Wojciech Banaś for work on the patch.
|
|
define get_absolute_url().
Thanks jukvalim for the report and initial patch,
and Preston Timmons for review.
|
|
|
|
|
|
|
|
|
|
|
|
Thanks raphael.herouart at gmail.com
|
|
|
|
|