|
-
October 28th, 2004, 12:46 AM
#1
Database Design

Let's pretend you have a CMS. This CMS allows has a blog (post, edit, delete) like method of managing files for others. You have a documents section, a downloads section, a picture section, an portfolio section, etc. All of these sections are sort of the same in the database. These are the columns:
ID - A index number according to this row
poster - Name of the person who posted
title - Title of post
the date - self explanatory
message- details, a text section
link - A link to the content, I.E. downloads section has a link to a file.
Now, there is also a News section... This news section's posts do not have a title, or link, which means those columns will be unused.
I feel like these are my choices:
-I have 1 table with all of the sections that contain content (titles, links), and another table for the news?
-I have 1 table with all of the sections, including news, and leave the link and title as null values in the news posts. I add a column to identify which section the row belongs to.
-I have a table for each section. This is my current setup, which I don't like.
Any ideas will be helpful. Thanks!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|