mirror of
https://github.com/django/django.git
synced 2025-08-09 21:38:18 +00:00
[1.6.x] Fixed #19560 -- Identified field in warning for naive datetime.
Thanks gcc for the report and vajrasky for the patch.
Backport of 570d9c2678
from master.
This commit is contained in:
parent
503092b09a
commit
ddff6522fa
3 changed files with 19 additions and 11 deletions
|
@ -431,14 +431,15 @@ code: :func:`~django.utils.timezone.now`,
|
|||
Finally, in order to help you locate code that needs upgrading, Django raises
|
||||
a warning when you attempt to save a naive datetime to the database::
|
||||
|
||||
RuntimeWarning: DateTimeField received a naive datetime (2012-01-01 00:00:00) while time zone support is active.
|
||||
RuntimeWarning: DateTimeField ModelName.field_name received a naive
|
||||
datetime (2012-01-01 00:00:00) while time zone support is active.
|
||||
|
||||
During development, you can turn such warnings into exceptions and get a
|
||||
traceback by adding the following to your settings file::
|
||||
|
||||
import warnings
|
||||
warnings.filterwarnings(
|
||||
'error', r"DateTimeField received a naive datetime",
|
||||
'error', r"DateTimeField .* received a naive datetime",
|
||||
RuntimeWarning, r'django\.db\.models\.fields')
|
||||
|
||||
Fixtures
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue