|
Posted by Trevor Best on 10/08/05 14:35
laurenq uantrell wrote:
> Is there any reason to have a row that is the PK/Identity and a row
> that is datatype Timestamp in the same table?
>
> Does this in any way help speeding up row updates?
>
> Thanks,
> lq
>
Timestamp is useful for checking if a row has been updated by someone
else since you read it, so you don't need to check every other column
value and compare.
It's also a good idea if you use Access (and possibly other) front-end
if you have any floating point data types (even dates) as floating point
errors can cause the front end to think the row has been updated by
someone else even if it hasn't. (You've no doubt seen in CDMA,
timestamps recomended as cures for such problems).
Navigation:
[Reply to this message]
|