Thank you all for all your suggestions and your quick responses. I think the 1.6-South idea would work, and likewise adding the field by hand using SQL.
Problem with sqlmigrate is that all we got now is the initial migration, with all the fields. We don't have a django migration for the new field, that's back in South and 1.6. In the meantime, I charged ahead with a dump, recreated db, and reloaded the data. Had to comment out the new field temporarily to do the dump. I do feel slightly dirty, but have done worse. I think it's ok, but we're doing a bunch of testing. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/10b9e7b8-5efe-4185-8026-4b11830645dc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
