You could do it that way but it is bad database design. Normalized design would be a poem table, a judge table and a relational table between the two. I would probably call it scores. That way you can have a poem can be judged by more than one judge, and each judge can score more than one poem.
Simpliest design would be; Poem Table: PoemId PoemAuthor PoemTitle Poem Content Judge Table: JudgeID Judge Name Score Table: PoemID JudgeID Score Also, if you have multiple poems by the same author, you might want an Author Table. In that case you would store the AuthorId in the Poem table instead of the Name. On Tue, Jan 25, 2011 at 12:32 PM, Adam Parker <[email protected]> wrote: > > What if I only use a "judges" table that includes the judgeID, poemId, and > score? Could I use this table to assign poems to judges using poemID and > judgeID? Then as the judge scores a poem, the score is recorded to the > judges table? > > Right now, I have an overview page that lists the poem title, avg score and > judge(s) assigned to review the respective poem. If the judges are edited, I > want it to modify the judges table and update the record. Then, when the > judges view the individual poem and rate it, the score with get populated. > > Would this work? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-newbie/message.cfm/messageid:5216 Subscription: http://www.houseoffusion.com/groups/cf-newbie/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-newbie/unsubscribe.cfm
