Re: Converting implicit m2m through table to explicit through model with Django 1.7 migrations

Thanks for the replies. Carsten - that link is broken for me unfortunately.

Thanks for the thumbs up Simon - appreciate the help. I'll be sure to document this once I have a moment. I have one follow up question. Both so I can see the proof in the pudding myself and because I'm generally curious about how all the magic happens, is there any way to inspect the state of the autodetector? By that I mean, I'd like to test that this is 100% equivalent to a standard migration solution (i.e. create new field, move data to new field, remove old field, create the field again, move the data back) by creating both sets of migrations (on separate branches of course) and checking the state the autodetector "thinks" it's in at the end of the migrations. Is that possible?

On Tuesday, September 29, 2015 at 12:09:25 PM UTC-4, Carsten Fuchs wrote:

Hi John,

Am 28.09.2015 um 15:54 schrieb John Lucas:
> So - is my approach safe? Or will there be complications down the line?

I've recently had a similar / the same question. See this thread, which also contains
the solution that worked very well for me:
http://thread.gmane.org/gmane.comp.python.django.user/172038

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+unsubscribe@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/b1e3a540-8fe1-4480-89a8-b7011bf5e277%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.