List:General Discussion« Previous MessageNext Message »
From:Chris Lott Date:July 1 1999 6:01pm
Subject:DB design for quotes and subjects
View as plain text  
I am building an app for an English Dept faculty member that is a kind of
literary quote encyclopedia using PHP and MySQL. I am trying to lay the best
design groundwork for growth. I plan to have a table of quotes and a table
of topics, etc. My question is: what is the best way to relate each quote to
its variable number of topics: simply a topic field with a list of ID's that
relate to the topic table? Or should there be topic1, topic2, etc columns
with the key? My worry with lists  is that it will be hard later to deal
with "weighting" the topics: ie sometimes one might want all quotes related
to topic "A" but other times one might want only quotes where topic "A" is
the primary topic (first in the list if using the list scheme).

@who: Chris Lott | chrisl@stripped | IT Specialist | University of
@where: p907.474.6350 | f907.474.6841 |
@quote: Philosophy n. A route of many roads leading from nowhere to nothing

DB design for quotes and subjectsChris Lott1 Jul
  • Re: DB design for quotes and subjectsjonathan michaels2 Jul
RE: DB design for quotes and subjectsUnknown Sender1 Jul