Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Simple Denormalized vs Normalized Example
Message
From
23/12/1999 18:36:43
 
 
To
23/12/1999 14:40:44
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00308138
Message ID:
00308271
Views:
24
>However, rates may change but these changes should not be reflected in callhist. How would you like it if rate changes affected calls you made a year ago? In this case, a denormalized relationship is needed.
>


I could be way off base here, but I don't consider this denormalization at all. Denormalization is when the same piece of information is stored in two places. IN the example you showed, the effective rate for the call, and the current rate are not the same piece of information, but two distinctly different concepts. If the values can vary independently, you have not denormalized, you have only created as many fields as you need to accurately reflect the state of things.
Erik Moore
Clientelligence
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform