Are you adding the field to the model or is the field is already there and you're just adding null=True to it's definition. In the second case, the *backwards* migration will require a default value for instances that have NULL value.
On 10 October 2010 00:49, Tim Diggins <tim.digg...@gmail.com> wrote: > Yes I'm setting blank=True and null=True. But, when I migrate using > South (I've added this field to an existing model), South complains > that the field has no default value... In this instance, it isn't that > important, but just wondering how I specify "NULL" in python in future > (I would normally guess None, but that won't help in this instance).. > Although it's not important I wondered how I can indicate to South > that the default value IS actually NULL - but maybe this is a South > question not a Django (core) question. > > -- > 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. > > -- Łukasz Rekucki -- 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.
