I would probably go for the 3-table layout.
First, if the goals are more typically graded 1 or 2 times per year, it
doesn't leave you with lots of wasted space for storing those grades,
comments, whatever.
Second, there's always the possibility that someone might need more -- for
example, a single goal graded six times each for two different departments.
Or maybe they add summer to it. Who knows.
Finally, it seems to me that this gives you more flexibility and power when
it comes to slicing and dicing the data for analysis or display.
Of course, I'm far from a SQL expert, but that's my $.02
--Ben Doom
Programmer & General Lackey
Moonbow Software
: -----Original Message-----
: From: Janine Jakim [mailto:[EMAIL PROTECTED]]
: Sent: Thursday, November 21, 2002 3:59 PM
: To: CF-Talk
: Subject: OT: Database design question
:
:
: hmmm- I am very into keepting my database relational, but am
: wondering what
: the best route for thi particular issue is...
: Heres' the scoop
: 1. One student can be working on many goals so I have 1 one to many
: relationships.
: 2. Each goal needs graded every marking period (up to 6 times a year)-
: these are not traditioanl grades but a long comments piece) So
: goals have a
: one to many relationship with the grades.
: I'm thinking the best way to handle it is to break it into 3 tables
: table one student info
: table 2 all the goals for the students hooked to students with
: the studentid
: table 3 all the grades for the goals hooked to goals by goalID
:
: My other option is to have 2 tables
: table one student info
: table two goals + 6 grading periods comment sections
: Thanks in advance for any input.
: j
:
:
:
:
:
:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Get the mailserver that powers this list at http://www.coolfusion.com
