Home/ Questions/Q 138643
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T07:17:48+00:00

Of course if I put enough rows eventually there will be a repeat. But

  • 0

Of course if I put enough rows eventually there will be a repeat. But let’s assume I choose a big enough id field.

I want to know if I can assume that the id uniquely identifies the row over time. And if the client sends me an id I want to be able to determine what row it refers or if the row was deleted (or if it is a fake id, but in that case I will not care telling, wrongly, that the row was deleted).

Please refer also to the following: if I restart the database, or backup and restore – will it be continue creating ids where it left – or may be it will decide to ‘fill in the holes’

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. If you have a ‘int not null auto increment primary key’ that you never reset, then yes IDs will not be reused.

    However, this raises an interesting question – what happens if you happen to reuse an old ID (even though it won’t happen by default in MySQL, but the human factor always counts) ?

    If your database is properly normalized, cascaded and constrained your application should be able to handle the reuse of an ID.

    Edit (since you edited your post, I’ll flesh out my answer), about this quote: ‘And if the client sends me an id I want to be able to determine what row it refers or if the row was deleted’. It’s always possible to determine what row an ID belongs to if it’s not deleted (kind of vital to be able to extract information out of your database).

    However if the row the id refers to is deleted, then it’s not possible to determine what row it belongs to… since it’s not there. If you need this I would advice you to implement some type of auditing functionality, preferably by triggers .

    • 0