If you mean, add the field/column - sort of. It was added to a database in use, I used dbmigration to handle the upgrade.
Regardless, I don't see why the loaddata command should choke on a null value for a Boolean if the models.py allows it. On Dec 6, 4:25 pm, ashwoods <[EMAIL PROTECTED]> wrote: > did u add that after a syncdb maybe? > > On 6 Dez., 21:55, Shev <[EMAIL PROTECTED]> wrote: > > > One of my models has a field like this: > > > confirm = BooleanField(blank=True, null=true) > > > When I use Django's dumpdata command to export my data to a fixture, > > and then try to re-import with loaddata, I see an error message that > > looks like this: > > > Problem installing fixture '/foo/bar/datadump.json': > > [u'This value must be either True or False.'] > > > I hand-edited the fixture file to change all the "null" values for the > > confirm field to "false" and the fixture loads fine. But shouldn't > > loaddata allow null to be in a BooleanField if the model definition > > allows it? (though all my other usages of BooleanField have a > > "default=" attribute, except this one) Has anyone else seen this > > problem? > > > Shev --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
