Simple DB Design Question

    Date: 09/04/07 (MySQL Communtiy)    Keywords: database

    I don’t quite understand how to best design a database…I was wondering if anyone would be willing to give me their thoughts.

    • It’s for an ever changing group of about 20 kids (they rotate yearly)
    • That can earn an occasionally changing list of 60+ awards

    (This is probably obvious) I want to pull down all the awards a child has earned and the date they earned it.

    Is there anything wrong with creating a single table with children listed in rows and awards listed in columns? 

    (It seems like its wrong—especially on a large scale, but I don’t know why I think that.)

    Thank You !

    Source: http://community.livejournal.com/mysql/117897.html

« Updating multiple tables... || Dynamic Tables »


antivirus | apache | asp | blogging | browser | bugtracking | cms | crm | css | database | ebay | ecommerce | google | hosting | html | java | jsp | linux | microsoft | mysql | offshore | offshoring | oscommerce | php | postgresql | programming | rss | security | seo | shopping | software | spam | spyware | sql | technology | templates | tracker | virus | web | xml | yahoo | home