On Tue, Feb 2, 2010 at 9:41 PM, Andrew Turner <acturne...@gmail.com> wrote: > On Feb 2, 1:29 pm, Russell Keith-Magee <freakboy3...@gmail.com> wrote: >> The cause of the problem is your initial fixture. Django doesn't >> listen to auto_now_add or auto_now fields on fixture loading - fixture >> objects are saved in "raw" mode, so it is assumed that the fixture >> should have data for all the fields. In this case, your fixture is >> missing a definition for pub_date, so on the second sync, you are >> getting the error I would expect - that the null value in the column >> isn't allowed. > > I see. As stated in my original post, syncdb works the second time > round when auto_now=True is used. Surely that shouldn't work at all > either?
Correct. I'm guessing that the same thing is happening - the default value is being used because the fixture doesn't specify a value. Feel free to update the ticket so the auto_now case isn't forgotten. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
