>I have a primary key listed as ID
>
>When I first added about 10 records and then deleted a few records and
>then added more records it didn't replace the missing records.
>
>When I select all records to view I now get:
>
>1
>2 why didn't it go to 3, 4 and 5 after 2?
>6
>7
>8
>
>
>
>When I add a
How I learned to love number gaps:
I have a database of colleges and universities. Every degree listing
as a numbered id. This used to be auto-incremented. After several
deletes and additions, I found it advantageous to have gaps between
schools to add new degree listings, so that I didn't get
> How would you actually overcome that? Wouldn't it be good if
> MySQL would be adapted to actually do this for you?
I think that not reusing deleted numbers is easier (i.e. more efficient).
IIRC, earlier versions of MySQL in fact reused the numbers.
There are 2 ways to overcome this:
1) Check
No, what is meant here is that:
He has record 1 2 3 and 4. Now deletes 2 and 3. Now create 2 new records. MySQL
creates them as 5 and 6, instead of 2 and 3 again...
--Kobus
>>> Lindsay Adams <[EMAIL PROTECTED]> 2001-04-08 19:42:12 >>>
I can understand not wanting to have holes, but..
If it is
How would you actually overcome that? Wouldn't it be good if MySQL would be adapted to
actually do this for you?
-- Kobus
>>> "Jens Vonderheide" <[EMAIL PROTECTED]> 2001-04-08 19:25:48 >>>
> When I first added about 10 records and then deleted a few records and
> then added more records it did
I can understand not wanting to have holes, but..
If it is a primary key, how are you going to handle updating tables that
rely on that key id?
If your id numbers were to shift, like you want, and you had a related sub
table (one to many) and this was say, an shopping cart, then all of a sudden
> When I first added about 10 records and then deleted a few records and
> then added more records it didn't replace the missing records.
That's MySQL's usual behaviour. auto_increment only garantees to create
unique keys. "Holes" left by deleting data are not filled.
Jens