From 37d04889108bb4334b873fa8b0b017343e15c5a1 Mon Sep 17 00:00:00 2001 From: Karen Tracey Date: Tue, 13 Mar 2012 00:15:43 +0000 Subject: [PATCH] Add a note to the backwards-incompatible changes section of 1.4 release notes about the change related to loading fixtures with incomplete data for auto_now and auto_now_add fields. Refs #12753. Thanks ptone. git-svn-id: http://code.djangoproject.com/svn/django/trunk@17694 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/releases/1.4.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt index 1e3c6032b2..393df5401f 100644 --- a/docs/releases/1.4.txt +++ b/docs/releases/1.4.txt @@ -1078,6 +1078,16 @@ The internals of the tag aren't part of the official stable API, but in the interests of full disclosure, the ``ExtendsNode.__init__`` definition has changed, which may break any custom tags that use this class. +Loading some incomplete fixtures no longer works +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Prior to 1.4, a default value was inserted for fixture objects that were missing +a specific date or datetime value when auto_now or auto_now_add was set for the +field. This was something that should not have worked, and in 1.4 loading such +incomplete fixtures will fail. Because fixtures are a raw import, they should +explicitly specify all field values, regardless of field options on the model. + + Features deprecated in 1.4 ==========================