Creating new table vs adding new field

Question

0.00/5 (No votes)

See more:

I am having following data :

Fabric Cost

time     |   No fabric|BangloreSilk|Chanderi|.... <- fabric types
--------------------------------------------
01/15    |         40 |         25 |...
02/15    |         45 |         30 |...
.....    |        ... |        ... |...

Dyeing Cost

time     |   No fabric|BangloreSilk|Chanderi|.... <- fabric types
--------------------------------------------
01/15    |         40 |         25 |...
02/15    |         45 |         30 |...
.....    |        ... |        ... |...

And here list of fabric types will be same for both the data.

Now to add this data I created following tables :

fabric_type

id                  int
fabric_type_name    varchar

And then I have two approaches .
Approach 1 :

fabric_cost

id                  int
fabric_type_id      int (foreign key to fabric_type)

cost int

deying_cost

id                  int
fabric_type_id      int (foreign key to fabric_type)
cost                int

Approach 2 :

fabric_overall_cost

id                  int
fabric_type_id      int (foreign key to fabric_type)
cost                int
fabric_or_dyeing    bit (to represent 0 for fabric cost and 1 for dyeing cost)

Now the question is which approach will be better??

Posted 2-Aug-15 21:24pm

afzalex

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

DamithSL · Answer 1 · 2015-08-02T21:55:00

Solution 1

I would have use 3 table
1. FabricType
2. FabricCost
3. CostType

Cost type table you can have two entries now, you can add more in future if needed.
Primary Key of Cost Type and FabricType can used in Fabric cost table record as foreign keys.

Posted 2-Aug-15 21:55pm

DamithSL