title: Unexpected ID offset in tables after transaction
body: <p>Ive basically done a transaction in two different functions, in my code which are called back to back. The code is written entirely in PHP using MySQL.</p>
  
  <pre><code>insert_into_table1()
  {
       // transact start
       // perform delete from table1
       // insert into table from select statement from the database
       // commit if done, else rollback
  }
  
  insert_into_table2()
  {
       // transact start
       // perform delete from table2
       // insert into table data from table1 after some processing (but same number of rows)
       // commit if done, else rollback
  }
  </code></pre>
  
  <p>The above is an example of the psuedo-code.
  <strong>Initially, tables are empty.</strong> 
  The issue arises, after the code runs. Both tables get inserted with N number of rows. </p>
  
  <p>When the code is run again, the tables are emptied using the delete command (MySQL). And N number of rows are inserted again into both tables.</p>
  
  <p>But after the second (or more) run, the 'id' (I have this on auto_increment with offset 1 for both tables. Ive confirmed that the value doesn't change) field of table1 continues with N+1, but there is an offset of 10 for the second table whereas it should also continue with N+1.</p>
  
  <p>I would like to know why this behavior occurs and how to fix it. </p>