title: Flask-migrate : How do I manage db of other installed modules
body: <p>I in the process of setting up Flask-migrate on an existing project. My project also uses Taskflow (<code>https://github.com/openstack/taskflow</code>) module.</p>
  
  <p>Taskflow sets up its own tables. All this while I have been pointing taskflow to use the same db as the app and it creates its own 3 tables. Now with migrations enabled, I am getting this error</p>
  
  <p>Can't locate revision identified by '397d0bf4d081'</p>
  
  <p>[This is happening when I do upgrade of the taskflow backend connection - if that is of any significance]</p>
  
  <p>I am not clear as to how migrations should be setup to manage tables of the packages/modules that are installed in the project.</p>
  
  <p>As I was writing this question, I got the idea to point the module to itw own db.</p>
  
  <p>I tried this and it works. The question boils down to what is the right approach - Whether DB requirements of installed modules should be managed by pointing it to separate db (appears like the right thing to do).</p>