Re: table design for customer rates.

From: bernard (bernard_at_bosvark.com) <bernard_at_bosvark.com>
Date: 17 Aug 2006 02:33:03 -0700
Message-ID: <1155807183.896652.115920@i42g2000cwa.googlegroups.com>

zubairpam_at_gmail.com wrote:
> currently, i'm using two techniques
>
> 1. each customer have seperate tables

Bad idea, this is not following a relational model.

> 2. two tables - one for (CourierType, TypeID)
> (DocFirstHalfKG, DocAddnHalfKG, ParFirstHalfKG, ParAddnHalfKG --> 01,
> 02, 03,04) corresponding
> second table :
> (TypeID, Countries(rows starting from A to Z all countries like
> Algeria,Argentina... Zimbawbe), CustomerID)

You need to identify the entities and elements of your business and do data normalization. Start with a logical model and derive a physical model from that. (Best tool is JDeveloper plus it is free) Entities: Couriers, Customers, Countries Attributes: Courier Type

> If i use the first one, the database increasing tremendously.
> In the case of another, many fields are blank.

Better to live with blank fields on few (manageable) tables than many small tables.

> I'm looking for any best solution to the above problem.
> Thanks in advance for your help.

See http://orafaq.com/faqdesgn.htm#NORMAL and follow links at the bottom of the page.

Regards
Bernard Received on Thu Aug 17 2006 - 04:33:03 CDT