Posted by Kenneth Downs on 05/15/06 04:13

Jerry Stuckle wrote:

> Kenneth Downs wrote:
>> Bent Stigsen wrote:
>>
>>
>>>
>>>The answer is D, implementing two tables.
>>>One table with the characteristics, and one table containing two foreign
>>>keys making the association between characteristics and the "items" (what
>>>that might be).
>>
>>
>> Anybody working with databases must have a reasonable method for altering
>> table structures as a regular event and a reasonable way to synchronize
>> structures and the code that works with them. Not having this will cost,
>> and all solutions that seek to re-invent physical implementation produce
>> burdens worse than the disease.
>>
>
> I disagree. If you properly plan your installation, you will not need to
> change
> your tables. Over the years I've designed hundreds of databases; most of
> them have never been changed.

Sorry to hear that.

>
> Having to alter a database layout either means you've had a significant
> change in the database needs, or, more likely, you didn't design it
> properly in the first place.

Or your customer loved it, their business is growing, and they've got more
stuff for you to do.

Cheers,

--
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth@(Sec)ure(Dat)a(.com)

[Back to original message]