On Thu, 2007-12-06 at 14:38 -0800, Shev wrote: [...] > Regardless, I don't see why the loaddata command should choke on a > null value for a Boolean if the models.py allows it.
This is a mistaken assumption. Since some of the constraints specified in models.py are enforced at the database level, if your database column does not exactly match what is in models.py, you will see errors. Django cannot (will not) override the database in that respect. I don't know if your original error was raised from the database server or before it got to that point, but it's quite possible and normal for something to be impossible because the database column doesn't permit it, even if you've messed around with models.py to allow it. Malcolm -- Many are called, few volunteer. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
