If your database has a primary key, then you could only update a row in the 'interior' and would have to move all the other rows.. this is called an insertion anomaly...
HOWEVER,
databases do not store records (called tuples) in any specific order... that is the purpose of SQL,.. to sort depending on xyz criteria..
You have to design your database with these issues in mind:
What happens if I insert a record?
What happens if I delete a record?
What happens if I update a record?
In general, in good relational database design, records with duplicate values/entries in two or more rows are moved to their own table, and joined together through SQL queries.... however MySQL is very forgiving and does not use relationships or foreign keys..
If the id's are a problem, add a second id column.. the first can be primary with auto_increment values, the second can be updated if need be, and consecutively numbered.. but this is very unnecessary if you can write decent sql..
Have phun 😉