Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 895725
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T14:36:19+00:00 2026-05-15T14:36:19+00:00

I am pretty new in data base design and I would like have your

  • 0

I am pretty new in data base design and I would like have your opinion :-).
I need design a simple Data Base for a CMS, CMS will manage Articles and Blog Posts for my website.
My Questions:

A)
Since fields in DB for Articles and Blog Posts are the same (ex: Title, Main content) expect “Type” (Posts or Full-Articles), I thought would be a good design solution to have a single Table “Pages” and associate a Look Up table for “Type”.

  • It is a good design solutions?
  • Where to place a Clustered Index to improve performance?

B)
Articles and Blog Posts could have property like “Top Article” or “Editor Choice”.
I thought to manage this property adding a Field to table “Pages” like “IsTop Article” and “IsEditorChoice”.

  • It is a good design solutions?
  • Could make sense use a separate Table and associate a FK for these fields?
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T14:36:20+00:00Added an answer on May 15, 2026 at 2:36 pm

    When designing a database, determine what are your data elements (Articles, Posts) and what are attributes of the data elements (type, top article, editor choice).

    Attributes that will always be present, like “type” can have their own column in the data elements table since they will always be populated. If data elements can have more than one “type”, then you need to separate the “type” out into a separate table (one to many relation).

    Attributes like top article and editor choice are not associated with every data element, so they should be in a separate table. Think of them more as categories. By having them in a separate table, instead of a column, you can easily add “categories” without modifying the table structure.

    I would suggest a basic structure like this:

    content
    content_categories (relation between content and categories)
    categories
    content_type (relation between content and type)
    types
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm pretty new to programming and html design and would like to ask a
I'm pretty new to Servlets and JSP and to using databases. At the moment
I'm looking for help identifying this design pattern and learning the typical vocabulary it
I have an Access 2007 application (previously in Access 2003) that is running into
I have looked and thought about good and bad points of my past designs
I've got 2 applications using Core Data with a sqlite persistent store. I've got
Preface: I was thinking the other day about a new database structure for a
Having a background in Haskell I am currently trying to get familiar with Scala.
I am reviewing / redesigning / refactoring a database and want to create a
I've got the following function: public function already_tweeted($tweet){ return mysql_num_rows(mysql_query(SELECT * FROM `retweeted` WHERE

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.