Received: from megamail.dsl.net (megamail.dsl.net [209.87.64.97]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6RKk5f54094; Fri, 27 Jul 2001 16:46:05 -0400 (EDT) (envelope-from james@lrgmail.com) Received: from jameslt (64-51-205-180.client.dsl.net [64.51.205.180]) by megamail.dsl.net (8.9.3/8.9.3) with SMTP id QAA05712; Fri, 27 Jul 2001 16:45:50 -0400 Message-ID: <00ce01c116dd$d83f5fe0$1600000a@lrg.office> From: "James Orr" To: "Gonzo Rock" , Cc: References: <3.0.5.32.20010727110215.00c9bac0@postoffice.pacbell.net> <3.0.5.32.20010727132144.009eae90@postoffice.pacbell.net> Subject: Re: Database Design Question Date: Fri, 27 Jul 2001 16:51:00 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Archive-Number: 200107/362 X-Sequence-Number: 4176 ----- Original Message ----- From: "Gonzo Rock" To: Cc: Sent: Friday, July 27, 2001 4:21 PM Subject: RE: [SQL] Database Design Question > OK... Fair Enough... Good Points indeed y'all. > > Well... What about the problem of users trying to Query the Database?? > > You know... like when using Crystal Reports or something?. > > SELECT * from HistoryTable > WHERE PartID = SomeInteger > > vs > > SELECT * from HistoryTable > WHERE PartNum = 12345636 AND PartRev = C > > How are they supposed to know What the PartID is ?? > > Anyway, that I why I was considering changing... current users always have trouble peering into the database... They don't quite get it. Search conditions don't HAVE to be indexes. And you can have more than one index. So you could have your primary index on PartID, which would be used by your applications and another index on PartNum and PartRev if those are frequently searched fields for crystal reports etc.