Thanks for the comment Matt. I wasn't trying to change anything in the database, it was just that Django wanted the django_migrations table to exist, but it didn't, and the db was read-only for safety during testing. Could well be that I wasn't using fake properly, I'm not sure, but I'd still prefer to have had the option to disable migrations entirely since in our case, they're too simplistic for migrating large tables with minimum downtime.
Either way - we recently hit another Django limitation - as best I've been able to tell, joining a table with itself seems to be very poorly supported - so we're heading towards SqlAlchemy, and probably away from Django altogether in time. Good luck with your migration! On Wednesday, 20 April 2016 23:25:31 UTC+10, Matt Schinckel wrote: > > On Wednesday, December 2, 2015 at 6:31:31 PM UTC+10:30, john....@gmail.com > wrote: >> >> +1 for disabling migrations completely - for several reasons. >> >> 1. Right now, I'm trying to run tests against a production database with >> runserver, in *read-only* mode - but it fails because it can't create the >> django_migrations table. (I'm in the process of upgrading from Django 1.4 >> to 1.8, so the table doesn't yet exist in production.) >> > > 2. Our mysql database is 3TB, with some tables of up to 500GB - and I >> assume that migrating them with Django - without taking the system down for >> days - is not possible. Instead, we use Percona's pt-online-schema-change, >> which does an excellent job of migrating big tables, whilst keeping them >> fully usable with no downtime. >> > > When upgrading from 1.4 to 1.7+, you shouldn't be changing anything in the > database. Sure, you'll want to build up the migrations, but you won't > actually want to apply them, only fake them. If you are attempting to > change your db structure at the same point in time as upgrading from > pre-1.7 to post-1.7, you are making it much harder than it needs to be. > (Yes, I'm going through the same process, with a database of similar size. > Mine is postgres though). > > -- 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/4c0697fb-2c0b-4d66-af33-5b335e611b08%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
