Well, I expect that just about everything would have the possibility of changing, save the
job site address, but that would be high up in the relation hierarchy, and not cause a lot
of duplication. Regardless, agreed - Complexity & Space. I think that with the relatively
small amount of data I expect them to store, and the size of hard drives nowadays, I am
leaning to db structure simplicity.
"David Kerber" <ns_dkerber_at_ids.net> wrote in message news:3CF50F18.DE364842_at_ids.net...
> If you really wanted to get tricky with it, you could save that other
> info which wouldn't change from version to version of the quote in
> another table, but that may be more work than it's worth in space
> saved. At this point, it's really a decision you have to make with the
> trade-offs between application complexity, space usage and flexibility.
Received on Wed May 29 2002 - 13:33:38 CDT
