OpenEuphoria

RE: EDS Database indexing?

• Posted by Matthew Lewis <matthewwalkerlewis at YAHOO.COM> Jun 05, 2001
• 361 views

> -----Original Message-----
> From: Euman [mailto:euman at bellsouth.net]
 
> 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.

Personally, I'd just delete the entire record.  As far as EDS is concerned,
the records are 'automatically' moved up by one.  Don't confuse the record
number with the record key.  EDS automatically 'sorts' the records by their
keys.
 
> 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.

I'm a little confused regading your keys.  Are you using an [auto]number for
the key?  Also, what exactly are you referring to with regards to
re-indexing?  I don't understant your use of the word 'index'.  Do you mean
key, or maybe record number?  I don't understand the LIstView scenario
either.

Are you creating a [pseudo]relational database?  In other words, are you
relating the keys in your table to data in other tables?  If so, why would
you want to change the keys?

Is there a reason to have 'contiguous' keys?  I think you're making more
work for yourself.

Matt Lewis