timestamps (was: TIP, how to fight with corrupted indexing)

[Ruslan Zasukhin]

on 2/4/03 2:16 PM, Robert Brenstein at rjb at rz.uni-potsdam.de wrote:

>>> There
>>> is clearly a need for a mechanism that ensures that indexes are in
>>>  sync with data.
>> 
>> Yes, such mechanism will be so called TIMESTAMP -- internal time of
>> database. Each time is changed at least one field, value of tine is
>> incremented.
>> 
>> In 2.0 TIMESTAMP will present in each table in any case, for each record.
>> Because this is needed for our transaction model.
>> 
> 
> You mean that v-kernel will keep checking the timestamps and
> automatically rebuild index when it is out of sync (besides using the
> timestamps for transactions)? So each record will have a timestamp
> and then the table will have its own, right? And table's timestamp
> will reflect newest timestamp of its records and any
> structural/property changes to table, right?

Absolutely Robert!

Each record will have TIMESTAMP to support transactions.
This is our payment for transaction, 8 bytes per record.

And yes, Table header and Index header will have TimeStap of last change.
So Valentina will be able decide what indexes must be rebuild in case of
failure.


-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://listserv.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------