Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Best Practice: One table or three?
Message
From
06/12/2002 19:36:58
Hilmar Zonneveld
Independent Consultant
Cochabamba, Bolivia
 
 
To
06/12/2002 18:12:15
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00730522
Message ID:
00730544
Views:
13
>My current data design scheme has three tables (Funding, Payments, Charges) to handle financial data of different types. Each has a primary key, two foreign keys, date, amount and an additional field or three.
>
>I was going to make a change to all three tables when the obvious question hit me: Would I be better served to collapse all three into a single table?
>
>Any opinions to offer questions to explore on this?

One key question is: how similar are the structures. If the tables are similar enough (only a few fields vary), maintenance may be simpler if you combine them. You would need a "type" field, to say whether the corresponding record is a funding, a payment or a charge. C(1) should do.

OTOH, sometimes you are almost forced to combine somewhat dis-similar tables, to simplify relations.

HTH, Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform