Re: Database Design Question
От | James Orr |
---|---|
Тема | Re: Database Design Question |
Дата | |
Msg-id | 00ce01c116dd$d83f5fe0$1600000a@lrg.office обсуждение исходный текст |
Ответ на | RE: Database Design Question (Gonzo Rock <GonzoRock@Excite.com>) |
Список | pgsql-sql |
----- Original Message ----- From: "Gonzo Rock" <GonzoRock@Excite.com> To: <pgsql-general@postgresql.org> Cc: <pgsql-sql@postgresql.org> 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.
В списке pgsql-sql по дате отправления: