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 8650027
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 12, 20262026-06-12T13:42:51+00:00 2026-06-12T13:42:51+00:00

I wanted to know what is the better approach (performance wise) when working with

  • 0

I wanted to know what is the better approach (performance wise) when working with Yii and mysql tables:

  1. 1 table with ALL the columns
  2. multiple tables (distribute the columns across them) with foreign keys relations

basically, what i’m asking is:
Is there any performance degradation when a single table has many relations since Yii will fetch all the corresponding tables into the object when you do a query?

A more general question is: what is good practice and smarter approach when dealing with 1 vs multiple tables and foreign keys (again performance..)

  • 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-06-12T13:42:53+00:00Added an answer on June 12, 2026 at 1:42 pm

    If performance was the only criteria in your design strategy, you would choose 1. A very bad choice, that would give you a lot of problems in a later stage of your problems.

    Databases should be designed with normalization in mind, so without any doubt, you must choose option 2!

    Update

    Example of normalized and not normalized: suppose we have a table with dvd rentals, and want to keep track of who rented the dvd:

    flat table:

    CREATE TABLE DVD (
      DvdId INT NOT NULL AUTO_INCREMENT, 
      DvdTitle varchar(64),
      Rental1 varchar(64), 
      Rental2 varchar(64), 
      Rental3 varchar(64),
      Primary Key(DvdId)
    );
    

    There is room for 3 rental entries, after that there is trouble. Beside that, when there is a extra field needed for the phone number of the customers, 3 extra fields must be made.

    First step normalization:

    CREATE TABLE DVD (
      DvdId INT NOT NULL AUTO_INCREMENT, 
      DvdTitle varchar(64),
      Primary Key(DvdId)
    );
    
    CREATE TABLE Rentals (
      RentalId INT NOT NULL AUTO_INCREMENT, 
      DvdId INT NOT NULL, 
      CustomerName varchar(64),
      RentalDate DateTime,
      Primary Key(RentalId)
    );
    

    This is better, but still not fully normalized. What if a customer rents the same dvd twice. Then there would be a double customer entry in the rentals table.

    Final:

    CREATE TABLE DVD (
      DvdId INT NOT NULL AUTO_INCREMENT, 
      DvdTitle varchar(64),
      Primary Key(DvdId)
    );
    
    CREATE TABLE Rentals (
      RentalId INT NOT NULL AUTO_INCREMENT, 
      DvdId INT NOT NULL, 
      CustomerId INT NOT NULL, 
      RentalDate DateTime,
      Primary Key(RentalId)
    );
    
    CREATE TABLE Customers (
      CustomerId INT NOT NULL AUTO_INCREMENT, 
      CustomerName varchar(64),
      Primary Key(CustomerId)
    );
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I wanted to know what is better performance-wise: to put the conditions in the
Just wanted to know that which one will be better: creating a different container
I am learning mvc3 and I wanted to know which will be the better
Just wanted to know if it is better to have Accept-Encoding, gzip in request
Hi I wanted to know if this approach is right, or what should be
I just wanted to know if <img src=> hurts performance in asp.net? If yes,
I wanted know how the kernel is providing memory for simple C program .
Wanted to know if there was a way one could query shelveset details from
Wanted to know if someone had a suggestion on code or maybe there's a
I wanted to know about Data Type implementation in PHP so I need a

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.