Skip site navigation (1) Skip section navigation (2)

Re: db design question

From: Vijay Deval <deval(at)giaspn01(dot)vsnl(dot)net(dot)in>
To: jules(dot)alberts(at)arbodienst-limburg(dot)nl
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: db design question
Date: 2002-10-20 13:46:29
Message-ID: 3DB2B3B5.4E8CA02A@giaspn01.vsnl.net.in (view raw or flat)
Thread:
Lists: pgsql-novice
Hi Jules

What will happen to oid if you dump the table, upgrade PostgreSQL and
recreate tables? 

In case a company has more than one consultent, company is going to
feature in more than one tuples with different oid's.

It might be a better idea to have two tables. One table assigns serial
id number to company. Other table could have this serial id as one
attribute , along with other things like consultant name etc. This
should avert problem of repeating data.

It is quite possible that one consultant gives consultations to more
than one companies. In that case the data needs to be stored in three
tables.

Vijay

Jules Alberts wrote:
> 
> Hello everyone,

> 
> The colums street and state (and a lot more in real life) are the same.
> My idea for the new db was someting like this:
> 
>   company(name varchar(100))
>   employee(code int)
>   consultant(name varchar(50))
>         address(ref_oid OID, street varchar(100), state varchar(100))
> 
> In this way, I can store all the addresses together and find them with.
> SELECT * WHERE addres.ref_oid = company.oid;


In response to

Responses

pgsql-novice by date

Next:From: Erik PriceDate: 2002-10-21 02:22:54
Subject: Re: Big Picture
Previous:From: working4alivingDate: 2002-10-20 11:28:14
Subject: Re: Help with the big picture

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group