title: Flyway - SQL migration-scripts versions on multiple git branches
body: <p>In the project we use Flyway migration tool to develop db schema along with git history of those scripts.</p>
  
  <p>The idea is that each script number is prefixed with number increasing by the value of 10 and after that the name, so for example:</p>
  
  <ul>
  <li>0000_name_one.sql </li>
  <li>0010_name_two.sql </li>
  <li>0020_name_three.sql</li>
  </ul>
  
  <p>etc.</p>
  
  <p>However since we had to start working on multiple branches (two main branches are for example: <strong>master</strong> + <strong>master_ext</strong>) plus we have some <strong>dev-branches</strong> for time-consuming features - there is a problem with choosing right script's numbers.</p>
  
  <p>When having long-term <strong>dev-branch</strong> introducing few changescripts, when merging it to either <strong>master</strong> or <strong>master_ext</strong>, where someone had also introduced same numbers of different scripts we would have conflicts. (merge will probably succeed due to differences in names but flyway migration will fail)</p>
  
  <p>Is there any pattern or good practice how to maintain SQL scripts versions when working on multiple branches?</p>
  
  <p>Thanks in advance</p>