Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You may need even more tables depending on the data your going to store:</p> <ol> <li>What if you use a password policy in the future where a user cannot re-use a previously used password? </li> <li>Can a user have more than one email?</li> <li>Can a user belong to more than one group?</li> <li>Can a user have more than one phone number?</li> <li>Only one parent? Or two? Is the parent in the system? What information about the parent do you store?</li> </ol> <p>Storing thinks like this may be worth to store in its own individual table, which means that in the future it should be a lot easier to maintain. You need to think of how the system will change. As for performance, as already outlined it shouldn't be a problem as long as you create the correct indexes, and use the database correctly.</p>
    singulars
    1. This table or related slice is empty.
    1. POTable design for user's information as well as login credentials?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBenW
    1. USBenW
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POTable design for user's information as well as login credentials?
      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. VTUpMod
    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. VTAcceptedByOriginator
    1. COThanks. Well the tables i proposed in the Question were samples only the main idea was to understand better when you should split and have multiple tables against where it would or not affect the performance. I usually make a layout of my database before making anything else and usually use multiple tables but i've seen around many softwares and webapps that still prefer using a singles tables ... where it got me thinking wether i should keep my style to maintainbility or not for performance also from time to time i benchmark everything to see how it goes ... heheh im creppy :(
      singulars
      1. PO
      1. USPrix
    2. COWhat if your information column keeps growing with sometimes even odd things ? would you go for a new table ? for example: table A users credential table B users information (id, user_id, address, phone, parents, birthday_date, comments, situation, ts_created, ts_update) then you get new fields (special food, best movie, best car, women type) i mean they are users information but sort of unrelated to the main users information would you go for a new table like users personal info or something alike or keep it with the table users informations ? how big would go or have u got with the columns
      singulars
      1. PO
      1. USPrix
    3. COWouldn't worry about splitting tables up, as long as you index correctly, and normalize your database it shouldn't be an issue. If anything it should help some of the more complicated queries you may use. Generally you and others working on it will find it much easier if you normalize the database properly and follow the 'book', single tables can very quickly get out of hand!
      singulars
      1. PO
      1. USBenW
 

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