Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's important to make a distinction between a user and a person.</p> <p>A person has a name, address, DOB , other facts about him. A user has credentials, secret question, system rights, etc.</p> <p>Now, asking yourself what is the relationship between a user and person. As Brian above answered it is a good idea to separate the two into different classes and tables by default, because that will make it easier down the road.</p> <p>Here are some reasoning to break these out.</p> <ol> <li>A user will likely remain the same throughout it's existence, the person attached to the user may not be.</li> <li>The information about the person is rarely needed in the context of permissions and roles, so that is extra data that will be floating around in your user class unnecessarily. This list goes on...</li> </ol> <p>I generally break out the user stuff into the following classes</p> <pre><code> User ( id login password password_expiredate enabled otherflags ) //(occasionally email, if it is used as login) Person ( pid // If it is not one to one between user and person user_id FK Name DOB Email other relevant information ) Address ( person_pid type //home,work, etc Street City State Zip Country ) Phone ( person_pid type number ) </code></pre> <p>As for creating the classes, in general, I am not sure if it is good practice, but I allow the user to contain a person, which in turn contains the Address and Phone classes with the respective functions.</p> <p>In my experience, the normalization of the structure allow for flexible development of business rules that will use people and users.</p> <p>In addition, a person does not have to be a user.</p>
    singulars
    1. This table or related slice is empty.
    1. POPHP OOP User class
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USIkstar
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPHP OOP User class
      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
    1. COThanks for the nice post! Indeed, it is a nice idea to splits up in multiplce classes. But I think I won't create that much classes as you do. My aim is creating a CMS, so the information (like address) isn't that important. It probally will be used only on one page. So I'm not sure if it is intersting to split it up this far.
      singulars
      1. PO
      1. USWrite Down
 

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