Databases
StackOverflow2013
Postsdbo
POMysql creating lot of table or less tables, which is better?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMysql creating lot of table or less tables, which is better?
    primarykey
    data
    text
    <p>I am currently working on a webapp that is heavily depend upon lot of data from database. Consider the following case.</p> <p><strong>A) Table design with Predefined tables only</strong></p> <pre><code>1)table vehicle_type ------------------ id|name ------------------ 1 |car 2 |truck 3 |bike ------------------- 2)table users ------------------- id|name ------------------- 1 |James 2 |John 3 |Stefen ------------------- 3)table ownership -------------------------------- id|vehicle_type_id|user_id|count -------------------------------- 1 | 1 |1 |30 2 | 1 |3 |20 3 | 3 |2 |13 -------------------------------- </code></pre> <p><strong>B) Table design with dynamically creating tables using app logic, that is when a new entry comes in vehicle_type we create a new table with that name</strong></p> <pre><code>1)table vehicle_type ------------------ id|name ------------------ 1 |car 2 |truck 3 |bike ------------------- 2)table users ------------------- id|name ------------------- 1 |James 2 |John ------------------- 3)dynamic_table car ------------------- id|user_id|count ------------------- 1 |1 |20 2 |2 |10 ------------------- 3)dynamic_table truck ------------------- id|user_id|count ------------------- 1 |3 |15 2 |2 |20 3 |1 |12 ------------------- 4)dynamic_table bike ------------------- id|user_id|count ------------------- 1 |1 |4 2 |2 |12 ------------------- </code></pre> <p>In second case table vehicle_type act as key to dynamic tables. In first I used ownership the table to store the data of count of vehicle type that each owner has, in second I create dynamic tables for each vehicle type and stores each vehicle type count in seperate table.I think this approach will make the scaling of database relatively easy and querying much efficient,than using a single table ownership. </p> <p>I have never worked with large set of data but this one will have lot of data for sure. Please note above tables are used as sampels not part of real application logic. </p> <p>Please suggest the merits and demerits of each method.</p> <p>Thanks</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRohith Raveendran
    1. USRohith Raveendran
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMysql creating lot of table or less tables, which is better?
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COWhat exactly is a "dynamic" table?
      singulars
      1. POMysql creating lot of table or less tables, which is better?
      1. USypercubeᵀᴹ
    2. COIMHO, dynamic tables are not a good idea for any type of persistent data. They have a use for transient data for which you do not care about the long-term viability. In your case, I would define "large set of data". Mysql handles millions of rows just fine on this type of data with proper indexing.
      singulars
      1. POMysql creating lot of table or less tables, which is better?
      1. USDavid Fleeman
    3. CO@ypercube I am just referring tables created using application logic during when we need them.
      singulars
      1. POMysql creating lot of table or less tables, which is better?
      1. USRohith Raveendran
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload