Databases
StackOverflow2013
Postsdbo
POMySQL best approach for db normalising, relationships and foreign keys
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMySQL best approach for db normalising, relationships and foreign keys
    primarykey
    data
    text
    <p>There is an username/password verification step first then the database has following structure</p> <pre><code>^ is primary key * uses foreign key 1.StudentDetails table =========================================================================== ID^| Username | Password | Email | Address * | Website |Comments ====+============+==========+=============+===========+=========+========== 1 | xxxxxxxxxx | xxxxxxx | xx@xxx.xxx | 1 | http:// | text 2.Submissions table =========================================================================================== ID^|Username*|SubmitDate|SelectedCourse*|Price*|Promotion*|SubmitComments|SubmitStatus* ===+=========+==========+===============+======+==========+==============+================= 1 |xxxxxxxxx|2013-7-12 | int | int | int | text | int 3.SubmitComplete table ================================================== ID^| Username * | SelectionDate | SubmitStatus * ====+============+===============+================ 1 | xxxxxxxxxx | 2013-08-01 | int </code></pre> <p>Now I'm having an issue entering the address, when i try to enter the student details it won't accept until there is an address field, how best to tackle that? When i do an left join selecting certain fields from StudentDetails and certain fields from Addresses, addresses don't show.</p> <p>Im a mysql noob, so i'd like some guidance to see if the normalising and structure has been done correctly, or could it be done better, here is the <a href="http://sqlfiddle.com/#!2" rel="nofollow">fiddle</a> i couldn't get it to work properly, kept getting errors on the lines where i added the foreign keys, even though the building of the schema worked well on my machine.</p> <p>The fiddle console says error on line 2 but it looks to me it's actually on line 76. If there's anything i was unclear on, pls let me know. Thanks</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBob Machine
    1. USBob Machine
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COInstead of the user **name**, I'd use the user **id** as a foreign key in the submissions and submitcomplete tables. (and add an unique constraint on student.username)
      singulars
      1. POMySQL best approach for db normalising, relationships and foreign keys
      1. USwildplasser
    2. CO@wildplasser im not sure i understand u correctly, but if i do, that is what i did, u can see it in the fiddle Submissions.Username and SubmitComplete.Username both use StudentDetails.id as the key, what i had not done is the unique constrain.
      singulars
      1. POMySQL best approach for db normalising, relationships and foreign keys
      1. USBob Machine
    3. COHi Bob, I've prepared new fiddle for you. I didn't fill tables with values, just created them, but at the bottom you can see my comments to your fiddle. You may find the fiddle here http://sqlfiddle.com/#!2/c03dd
      singulars
      1. POMySQL best approach for db normalising, relationships and foreign keys
      1. USWirus
 

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