Author: kmtracey Date: 2012-03-12 17:15:43 -0700 (Mon, 12 Mar 2012) New Revision: 17694
Modified: django/trunk/docs/releases/1.4.txt Log: 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. Modified: django/trunk/docs/releases/1.4.txt =================================================================== --- django/trunk/docs/releases/1.4.txt 2012-03-12 23:05:16 UTC (rev 17693) +++ django/trunk/docs/releases/1.4.txt 2012-03-13 00:15:43 UTC (rev 17694) @@ -1078,6 +1078,16 @@ 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 ========================== -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
