Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Things to consider with your approaches</p> <p><strong>Storing User Profile in Users Table</strong></p> <ul> <li>This is generally going to be the fastest approach in terms of getting at the profile data, although you may have a lot of redundant data in here (columns that may not have any information in them).</li> <li>Quick (especially if you only pull columns you need from the db)</li> <li>Wasted Data</li> <li>More difficult to work with / maintain (arguably with interfaces such as PHPMyAdmin)</li> </ul> <p><strong>Storing User Profile in User_Profile Table 1-1 relationship to users</strong></p> <ul> <li>Should still be quite quick with a join and you may eliminate some data redundancy if user profiles aren't created unless a user fills one in.</li> <li>Easier to work with</li> <li>Ever so slightly slower due to join (or 2nd query)</li> </ul> <p><strong>Storing User Profile as properties and values in tables</strong></p> <p>*i.e. Table to store possible options, table to store user_id, option_id and value*</p> <ul> <li>No redundant data stored, all data is relevant</li> <li>Most normalised method</li> <li>Slower to retrieve and update data</li> </ul> <p>My impression is that most websites use the 2nd method and store profile information in a second table, its common for most larger websites to de-normalize the database (twitter, facebook) to achieve greater read performance at the expense of slower write performance.</p> <p>I would think that keeping the profile information in a second table is likely the way to go when you are looking at 50,000 records. For optimum performance you want to keep data that is written heavily seperated from data that is read heavy to ensure cache can work effectively.</p>
    singulars
    1. This table or related slice is empty.
    1. POMYSQL: User - profile details table setup - best practice
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USneopickaze
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMYSQL: User - profile details table setup - best practice
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthank you for this clear explanation.I think together with iddqd's answer, I will mix it and go for that option. - user table / profile table / stats table. Don't know who to select as answer now...
      singulars
      1. PO
      1. USrenevdkooi
 

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