Xref: utzoo comp.databases:6466 bit.listserv.sqlinfo:42
Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!eru!luth!sunic!dkuug!resam!andrew
From: andrew@resam.dk (Leif Andrew Rump)
Newsgroups: comp.databases,bit.listserv.sqlinfo
Subject: How do I handle wide SQL-tables
Message-ID: <1990Jul15.112644.676@resam.dk>
Date: 15 Jul 90 11:26:44 GMT
Organization: RESAM Project Office, SAS, CPHML-V
Lines: 32

I read in my (Oracle) SQL manual that I should keep my tables as "thin"
as possible but what do I do when I have a lot of information that only
has one key? The example below look a lot like what I have:

+------------------+------+------+-----------+----------+-------+-----+-...
! Social security# ! Name ! Born ! Telefone# ! Roadname ! Road# ! Zip ! ...
+------------------+------+------+-----------+----------+-------+-----+-...

This table gets quite wide - should I do anything with it?

The next question (I haven't got to that part of the manual yet so if you
are able to tell me where it is in Oracle 6.0 manual feel free to tell me!):
I use Pro*C and I want to be able to search on whatever the user enters,
like Name and birthdate (Born) or Name and Telefone# or ... Do I have to
make a SELECT for every possibility:

  select * from State where Name='Leif Andrew Rump' and Born='02-AUG-63';
  select * from State where Name='Leif Andrew Rump' and Telefon#='35822770';


Thank you in advance

Leif Andrew


Leif Andrew Rump, AmbraSoft A/S, Stroedamvej 50, DK-2100 Copenhagen OE, Denmark
UUCP: andrew@ambra.dk, phone: +45 39 27 11 77                /
Currently at Scandinavian Airline Systems                =======/
UUCP: andrew@resam.dk, phone: +45 32 32 22 79                \
SAS, RESAM Project Office, CPHML-V, P.O.BOX 150, DK-2770 Kastrup, Denmark

> > Read oe as: o <backspace> / (slash) and OE as O <backspace> / (slash) < <