On Apr 25, 5:09 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > this case you must run with > > DAL(....,migrate_enabled=True, fake_migrate_enabled=True) >
Does DAL(....,migrate_enabled=False, fake_migrate_enabled=True) work exactly the same as DAL(....,migrate_enabled=True, fake_migrate_enabled=True)? I don't think I fully understand migrate and fake_migrate. That said, the term "fake_migrate" sounds like a hack, an afterthought. The term sounds as if fake_migrate exists because migrate doesn't do a good job. Another thing is with 2 Boolean variables (migrate and fake_migrate), there are 4 possibilities, but it seems that 2 of those possibilities work exactly the same. If this understanding is true, can we simplify the situation and reduce 2 variables to 1. Say, call it "migrate", which has only 3 possibilities: (a) "off" - no migration, assuming models and pickled files are consistent. (b) "on" - migration, will attempt to insert/delete fields,tables to make picked files consistent with models. (c) "forced" - will force pickle files to be consistent with models, no matter what. This is equivalent to fake_migrate=True.
