Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Database design

Re: Database design

From: Van Messner <vmessner_at_netaxis.com>
Date: Thu, 13 Jan 2000 02:16:22 GMT
Message-ID: <Vzaf4.274$7F2.11284@tw11.nn.bcandid.com>


My contacts database has twenty one tables. It's pretty well normalized but since you're just starting I suggest you take a look at a book which lays out a basic corporate data model covering the standard ERP functions. Email me tomorrow at messnerv_at_ldcorp and I can give you the title and ISBN. You may find that putting contacts in a single table needs to be addressed before you worry about the length of fields. (You will be using varchar2, right?)

Van

Kenneth C Stahl <BlueSax_at_Unforgetable.com> wrote in message news:387CA134.D26FB1BF_at_Unforgetable.com...
> I have a rather odd request, but hopefully someone who reads this
newsgroup
> will know what I am looking for.
>
> I am in the process of designing a database from scratch based solely on
> the types of things that the customer is going to need.
>
> Since I don't have any previous database to reference I have to come up
> with the sizing of attributes for each of the entities.
>
> For example, I know that I will be dealing with an entity called a
CONTACT.
> One of the attributes for this contact will be an address. This address
can
> have several lines such as Suite, Street address, Room number, etc. etc.
> plus city, province/state, postal code, etc.
>
> Is there any univeral standard that defines attributes such as this? I
want
> to make my CITY attribute big enough to accomodate any possible city in
the
> world, but I don't want to make it too large. Also, while postal codes in
> the U.S. are 5-digits, I know that in other countries it is typically
> longer than that - so I would want to accomodate the largest possible
> postal code. For phone numbers I know that I'll have to deal with a
country
> code, an area code, an exchange/prefix and then the number as well as a
> possible extension. What I want to avoid is designing my database to only
> work with U.S. addresses and phone numbers.
>
> Although I've never actually worked with EDI myself, I have heard that it
> has established a standard for common attributes. Is this true? If so,
> would this be a reasonable standard to use?
Received on Wed Jan 12 2000 - 20:16:22 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US