On Tue, Feb 2, 2010 at 3:58 PM, Andrew Turner <acturne...@gmail.com> wrote: > On Jan 19, 1:36 pm, Andrew Turner <acturne...@gmail.com> wrote: >> I have an initial_data.json file which provides some, er, initial data >> whenever I run syncdb. One of my models has a DateTimeField with >> auto_now_add=True. The data is loaded first time round, but on >> subsequent syncdbs, I get "IntegrityError: posts_entry.pub_date may >> not be NULL". > > Anyone? Is this behaviour expected, or should I file a bug?
Well, it's difficult to know what is expected without more details. I can't think of any obvious reason why a fixture should fail on the *second* syncdb that doesn't also involve you doing something unexpected to your data in the interim. However, without any details of what else is in your models, or what else you have done to your data, it's impossible to say if you've found a bug or if you're doing something wrong. It is possible you've found a bug, but in order to verify that, we need a minimal example that reproduces the problem - that is, the simplest possible model and fixture combination that fails on the second syncdb like you describe. 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.
