Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Handling 1:M:M with views
Message
De
22/06/1999 07:52:41
Kenneth Downs
Secure Data Software, Inc.
New York, États-Unis
 
 
À
21/06/1999 16:32:39
Information générale
Forum:
Visual FoxPro
Catégorie:
Base de données, Tables, Vues, Index et syntaxe SQL
Divers
Thread ID:
00184085
Message ID:
00232396
Vues:
20
Gar,

>
>Nope -- it can be done with just the modest denormalization of propagating the parent key down the entire child, grandchild etc hiearchy. <

Let me stop you here. The objection is that the denormalization must occur from each level to all levels lower, which would become unmanageable. This is the only way to have a general solution in which any 1:M:M... form could "jump in" at level X and display/edit levels X, X+1, and X+3.

Consider your example of the Customer:Sales Order:Line Items. Let's extend it one more level to Customers:Sales Orders:Line Items:Shipping History. Assuming we have implemented a filter-based solution, then it should be easy to make a form that starts with customers and displays the complete 4 level 1:M:M:M heirarchy. However, tommorrow we may find a need to produce an abbreviated form that contains only Sales order:Line Items:Shipping History heirarchy. In that case, the surrogate key in Sales Orders would also have to be denormalized at each lower level.

In conclusion, then, a truly n-level general solution would require the surrogate key in every table except the bottom to be propogated all the way down. Hence my original statement that filtering causes the surrogate keys to multiply geometrically.

I agree that the solution works, but to my sense of aesthetics this denormalization appears too radical and leaves me still seeking a more palatable compromise.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform