This is impossible to occur unless you specifically and with intention aforethought defined the INTEGER PRIMARY KEY column with the attribute AUTOINCREMENT. If you did that, then this behaviour is EXACTLY the specific reason that the AUTOINCREMENT keyword exists in the first place. If you did not want this behaviour then you should not have used the AUTOINCREMENT keyword. Just because it "sounds cool" does not mean that it "works cool". It has a very specific meaning and very specific purpose. Unless you need to "carry out" the specific purpose, do not use the command for carrying out that purpose. Using a command because it sounds cool is kind of like ordering a firing squad to "fire" and then wondering why there are dead people piling up all over the place. What did you think would happen? Either that of you are not dropping the tables that you think you are dropping.