Thomas and Shawn, thanks for responding. South looks pretty useful - I hope that it could be included in the standard Django distribution.
On Tue, Jan 4, 2011 at 6:20 PM, Shawn Milochik <sh...@milochik.com> wrote: > You could do this with South in multiple steps. > > 1. South schema migration: > Add the new field for the proper foreign key, but don't make the field > required. > > 2. South data migration: > Create a migration that appropriately populates the new field based on > whatever rules you have. > > 3. South schema migration: > Make the new field required, and optionally delete the old field. > > Shawn > > -- > 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<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- Regards, Sithembewena Lloyd Dube -- 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.
