1. EDS Database indexing?
Hello all,
I need to make some changes to an EDS database
and need some advise.
Lets take an example:
If I have 8000 records and a user decides to delete record # 6999
should I leave the key alone and nullify the record space
or should I rewrite the database moveing all of the records
from the deleted record # 6999 to #8000 back one key.
The only difference would be the time to re-write the data
which really doesnt matter to me cause there is likely not going
to be more than 40-50k records. What concerns me is
latter down the road if I chose to use a ListView control
or a control that returns toplevel down record index's.
The second thing that concerns me is re-writeing the data,
would I risk the loss of data? thats what I asked myself.
I need alittle advise how to handle the key/data protions of
a mid sized database that compensates for records deletion
and re-indexing.
Please, any advise will help.
Euman
3. Re: EDS Database indexing?
Thanks Kat & Matt,
Matt you must be some sort of genious or something....
I've got enough here with what you said to take over
ORACLE hehe...;) I like the idea of saveing a seperate
table for indice retention, that makes since to go ahead
and put together.
Kat, I'll heed your warning about file re-writes.
"its better to be safe and slow than fast and sorry"
BTW, I like that "free" thing you put up there Kat ;)
that brought a smile to my face//
Euman
> when it's possible i can do it myself cleaner and freeer (freer? free-r?
free'r?).
> 
)
>
> Kat
