RE: Single Code Table or Separate Code tables dilemma

From: Jacques Kilchoer <Jacques.Kilchoer_at_quest.com>
Date: Fri, 23 Mar 2001 19:53:10 -0800
Message-ID: <F001.002D6F95.20010323193054@fatcity.com>

> -----Original Message-----
> From: Mandar Ghosalkar [mailto:MandarG_at_gsr-inc.com]
>
> i dont disagree with u. even i dont like the below mentioned
> implementations. i always prefer seperate tables. btw "lot of
> rows" is very
> subjective.

Of course. In my case, let's suppose I have hundreds of thousands of rows. In my opinion that's enough to think that having the values 'SPLT' and 'TYPE' in every row would be wasteful.

> i dont know what u mean by "I have to have a table that contains every
> possible combination of SPLT and TYPE. ".

I guess I don't understand what you mean when you say this:

"> but u can also create surrogate key and make (CODE_TYPE,
> CODE_VALUE) as
> alternate key (unique) and then reference the surrogate key
> in ur doctor
> table, instead of two cols as one foreign key"

What would the SQL statements look like? Received on Fri Mar 23 2001 - 21:53:10 CST