Hi Carl, Am 23.07.2015 um 18:28 schrieb Carl Meyer:
Overall I think it might be simpler to go with your initial approach. I'd first rename the old field to some other temporary name (you don't have to update any other code to use this name, as you'll commit all of these migrations in one commit, so nothing but the following data migration ever needs to know anything about this temporary name),
Thanks for clarifying the details regarding renaming! With this, this is the approach that I feel the most comfortable with and will try now.
Overall, many thanks for your thoughts and your detailed reply, it's very much appreciated and helps a lot!
Best regards, Carsten -- 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 http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/55B11F7B.1010805%40cafu.de. For more options, visit https://groups.google.com/d/optout.
