Database Reference
In-Depth Information
Logically, you may think that these records are removed permanently, and the rest of the
features will move up to take their place. However, this is not exactly what happens; these
records are simply marked as deleted in the geodatabase. Imagine if the geodatabase
shuffles all records after each delete operation; editing will be extremely inefficient. That
is why the geodatabase only marks the records as deleted and discards these records from
any future queries. So, what happens when you try to locate
Croton's
(object 14)? It
just so happens that the geodatabase has to go through all these records anyway and skip
through the ones marked as deleted. Although they are deleted, they are, in a way, slowing
down the query. This is illustrated in the following figure:
