Re: pro- foreign key propaganda?
Date: Wed, 21 May 2008 08:17:47 -0400
Anne & Lynn Wheeler <lynn_at_garlic.com> writes:
> part of the issue attempting to replace the bdam implementation was
> that it was highly efficient ... having collapsed the article unique
> key and the corresponding record pointer into the same value (however,
> there was significant maintenance activity ... so significant access &
> thruput was needed to justify the extensive care and
> support). problems also started creeping in when the number of
> articles started exceeding the size of the record ptr/key.
aka ... overloading a value with multiple characteristics can significantly improve runtime operation ... but can become an administrative burden to maintain the consistency of all the different characteristics.
reducing the number of different characteristics a value has to represent will reduce the consistency administrative burden but will typically increase the runtime overhead (navigating internal tables relating the different characteristics). Received on Wed May 21 2008 - 14:17:47 CEST