First of all, I'd like to thank both of you for linking to some VERY helpful sources (plenty of which was above my head)!

I'm still feeling a little lost though. I've read the two sources linked here, and I've also looked at the XMBC wiki on their databases (which, I must say, made me more confused than I thought I was before I looked at it).

Perhaps someone can help me sort this out.

TV Show
- Image
- First Aired
- Genre
- Rating
- Etc.

Then for each show, I want to have (and be able to display) information for each season, and for each episode.

Episode
- Season #
- Episode #
- Episode Name
- Image
- Aired
- Overview

Season
- Image
- Season #?
- Show? (by some UUID?)

This information would be gathered and stored.

These fields/information would be gathered and populated by myself/my system. User posts would then be linked to either an episode OR a season (so a post made for a season wouldn't be linked to an episode). And have it's own set of 2-3 fields.

If I want users to be able to search for a show, see an array of the seasons in that show and the episodes within each season, then go to a particular season or episode post, should I have each of these as separate tables?

Tables: (1) Shows, (2) Seasons, (3) Episodes, (4) Posts
...with each "Seasons" entry having a field linking it to a "Shows" entry, each "Episodes" entry having a field linking it to a "Seasons" entry, and each "Posts" entry having a field linking it to a particular "Seasons" or "Episodes" entry?

Or should I have Seasons and Episodes under one umbrella "Shows" entry.
Tables: (1) Shows, (2) Posts
...and if so, how do I populate that with season and episode entries (I can only really link of a "[[episode for episode in season] for season in show]" kind of thing, which (if I understand correctly), is NOT how I want to do this, but is more...intuitive for myself (likely a sign that it isn't the best way to do this).

It seems like with the first method, more overall data would be involved/used, because:
(1) More fields are required to link everything together.
(2) Each time a complete array is displayed, the SQL table would have to query each entry, combining them into a completed array.
No?

Extraneous Question:
Why does the XMBC database system use such odd columns such as c00, c01, c02, c03, etc.?
Robin Hood Reviewed by Robin Hood on . How Should I Organize My SQL Tables? I'm sorry, I'm sure this is a complete n00b question, but I've been working with collecting data, and I'm starting to get to the point where I'd like to start populating a database, but I can't figure out what system will work best. Final Project: Dealing with TV Shows and information from the database... TV Show - Seasons - Episodes in season (for episode in each season) - Information about episode in season Rating: 5