if you have a users table, u_id (auto increment, primary) , username
And you have a messages table: m_id(auto_inc, primary), u_id
If you delete a user from the table, and you make the ID's continuous, your messages table will mixed.
And on a normal website you will work not just 2 connected tables... News, polls, relations, private contents ect...
If you wanted to make a continous order , make another field in that table. A primary key should never change, the primary key identifies the
row for all time,
Use a field to store an order-property of the row and update that. Set it to the next
maximum value on insert, shift it down on deletes.
Hello, jjozsi