A new name might not be a bad idea both because fake_migrate isn't that clear and it does sound hacky.
I've just rolled my database into production and have been struggling with migrations so any extra clarity would really help. It seems to me that something like "rebuild metadata" should be triggerable from admin? Is there a discussion anywhere on how to use the various settings and database log files to administer a production DB? For example, my sql.log file is a few thousand lines long now, mostly with duplicate failed migrations. And I have duplicate .table files now which Im not sure what to do with. And what migrations to avoid and how to do them if you have to?
