Web Programming Step by Step

Lecture 24
SQL Joins and HTML Tables

Reading: 11.4 - 11.5; Appendix A; 2.2.2

References: SQL syntax reference, w3schools tutorial

Except where otherwise noted, the contents of this presentation are Copyright 2009 Marty Stepp and Jessica Miller.

Tables: <table>, <tr>, <td>

A 2D table of rows and columns of data (block element)

<table>
	<tr><td>1,1</td><td>1,2 okay</td></tr>
	<tr><td>2,1 real wide</td><td>2,2</td></tr>
</table>

• table defines the overall table, tr each row, and td each cell's data
• tables are useful for displaying large row/column data sets
• NOTE: tables are sometimes used by novices for web page layout, but this is not proper semantic HTML and should be avoided

Table headers, captions: <th>, <caption>

<table>
	<caption>My important data</caption>
	<tr><th>Column 1</th><th>Column 2</th></tr>
	<tr><td>1,1</td><td>1,2 okay</td></tr>
	<tr><td>2,1 real wide</td><td>2,2</td></tr>
</table>

• th cells in a row are considered headers; by default, they appear bold
• a caption at the start of the table labels its meaning

Styling tables (3.2.6)

table { border: 2px solid black; caption-side: bottom; }
tr { font-style: italic; }
td { background-color: yellow; text-align: center; width: 30%; }

• all standard CSS styles can be applied to a table, row, or cell
• table specific CSS properties:
  • border-collapse, border-spacing, caption-side, empty-cells, table-layout

The border-collapse property

table, td, th { border: 2px solid black; }
table { border-collapse: collapse; }

• by default, the overall table has a separate border from each cell inside
• the border-collapse property merges these borders into one

The rowspan and colspan attributes

<table>
	<tr><th>Column 1</th><th>Column 2</th><th>Column 3</th></tr>
	<tr><td colspan="2">1,1-1,2</td>
		<td rowspan="3">1,3-3,3</td></tr>
	<tr><td>2,1</td><td>2,2</td></tr>
	<tr><td>3,1</td><td>3,2</td></tr>
</table>

• colspan makes a cell occupy multiple columns; rowspan multiple rows
• text-align and vertical-align control where the text appears within a cell

Column styles: <col>, <colgroup>

<table>
	<col class="urgent" />
	<colgroup class="highlight">
		<col /><col />
	</colgroup>
	
	<tr><th>Column 1</th><th>Column 2</th><th>Column 3</th></tr>
	<tr><td>1,1</td><td>1,2</td><td>1,3</td></tr>
	<tr><td>2,1</td><td>2,2</td><td>2,3</td></tr>
</table>

• col tag can be used to define styles that apply to an entire column
• colgroup tag groups several columns to apply a style to all of them

Don't use tables for layout!

• (borderless) tables appear to be an easy way to achieve grid-like page layouts
  • many "newbie" web pages do this (including some of our old web pages...)
• but, a table has semantics; it should be used only when you are actually representing a table of data
• instead of tables, use divs, widths/margins, floats, etc. to perform layout as much as possible

• tables should not be used for layout!
• Tables should not be used for layout!!
• TABLES SHOULD NOT BE USED FOR LAYOUT!!!

Database design principles (Appendix A)

• database design : the act of deciding the schema for a database
• database schema: a description of what tables a database should have, what columns each table should contain, which columns' values must be unique, etc.
• some database design principles:
  • keep it simple, stupid (KISS)
  • provide an identifier, or key, by which any row can be uniquely fetched
  • eliminate redundancy, especially redundancy of lengthy data (strings)
    • when redundancy is needed, integers are smaller than strings and better to repeat

First database design

• what's good and bad about this design?
  • contains redundancy (name, email, course repeated frequently)
  • there is no "key" column unique to each row

Second database design

• splitting data into multiple tables avoids redundancy
• normalizing: splitting tables to improve structure and remove redundancy / anomalies
• normalized tables are often linked by unique integer IDs

Related tables and keys

• records of one table may be associated with record(s) in another table
  • record in Student table with student_id of 888 is Lisa Simpson's student info
  • records in Grade table with student_id of 888 are Lisa Simpson's course grades
• primary key: a table column guaranteed to be unique for each record

Design question

• suppose we want to keep track of the teachers who teach each course
  • e.g. Ms. Krabappel always teaches CSE 142 and INFO 100
  • e.g. Ms. Hoover always teaches CSE 143
  • e.g. Mr. Stepp always teaches CSE 190M
• what tables and/or columns should we add to the database?

Design answer

• add a teachers table containing information about instructors
• link this to courses by teacher IDs
• why not just skip the teachers table and put the teacher's name as a column in courses?
  • repeated teacher names are redundant and large in size

Example simpsons database

Querying multi-table databases

When we have larger datasets spread across multiple tables, we need queries that can answer high-level questions such as:

• What courses has Bart taken and gotten a B- or better?
• What courses have been taken by both Bart and Lisa?
• Who are all the teachers Bart has had?
• How many total students has Ms. Krabappel taught, and what are their names?

To do this, we'll have to join data from several tables in our SQL queries.

Cross product with JOIN (11.4.1)

SELECT column(s) FROM table1 JOIN table2;

SELECT * FROM students JOIN grades;

• cross product or Cartesian product: combines each row of first table with each row of second
  • produces M * N rows, where table 1 has M rows and table 2 has N
  • problem: produces too much irrelevant/meaningless data

Joining with ON clauses (11.4.2)

SELECT column(s)
FROM table1
     JOIN table2 ON condition(s)
     ...
     JOIN tableN ON condition(s);

SELECT *
FROM students
     JOIN grades ON id = student_id;

• join: a relational database operation that combines records from two or more tables if they satisfy certain conditions
• the ON clause specifies which records from each table are matched
• often the rows are linked by their key columns

Join example

SELECT *
FROM students
     JOIN grades ON id = student_id;

• table.column can be used to disambiguate column names:

  SELECT *
  FROM students
       JOIN grades ON students.id = grades.student_id;
  

Filtering columns in a join

SELECT name, course_id, grade
FROM students
     JOIN grades ON students.id = student_id;

• if a column exists in multiple tables, it may be written as table.column

Giving names to tables

SELECT name, g.*
FROM students s
     JOIN grades g ON s.id = g.student_id;

• can give names to tables, like a variable name in Java
• to specify all columns from a table, write table.*

Filtered join (JOIN with WHERE) (11.4.3)

SELECT name, course_id, grade
FROM students s
     JOIN grades g ON s.id = g.student_id
WHERE s.id = 123;

• FROM / JOIN glue the proper tables together, and WHERE filters the results
• what goes in the ON clause, and what goes in WHERE?
  • ON directly links columns of the joined tables
  • WHERE sets additional constraints such as particular values (123, 'Bart')

Multi-way join

SELECT c.name
FROM courses c
     JOIN grades g ON g.course_id = c.id
     JOIN students bart ON g.student_id = bart.id
WHERE bart.name = 'Bart' AND g.grade <= 'B-';

• grade column sorts alphabetically, so grades better than B- are ones <= it

A suboptimal query

• What courses have been taken by both Bart and Lisa?

  SELECT bart.course_id
  FROM grades bart
       JOIN grades lisa ON lisa.course_id = bart.course_id
  WHERE bart.student_id = 123
        AND lisa.student_id = 888;
  

• problem: requires us to know Bart/Lisa's Student IDs, and only spits back course IDs, not names.
• Write a version of this query that gets us the course names, and only requires us to know Bart/Lisa's names, not their IDs.

Improved query

• What courses have been taken by both Bart and Lisa?

  SELECT DISTINCT c.name
  FROM courses c
       JOIN grades g1 ON g1.course_id = c.id
       JOIN students bart ON g1.student_id = bart.id
       JOIN grades g2 ON g2.course_id = c.id
       JOIN students lisa ON g2.student_id = lisa.id
  WHERE bart.name = 'Bart'
        AND lisa.name = 'Lisa';
  

Practice queries

• What are the names of all teachers Bart has had?

  SELECT DISTINCT t.name
  FROM teachers t
       JOIN courses c ON c.teacher_id = t.id
       JOIN grades g ON g.course_id = c.id 
       JOIN students s ON s.id = g.student_id
  WHERE s.name = 'Bart';
  

• How many total students has Ms. Krabappel taught, and what are their names?

  SELECT DISTINCT s.name
  FROM students s
       JOIN grades g ON s.id = g.student_id
       JOIN courses c ON g.course_id = c.id
       JOIN teachers t ON t.id = c.teacher_id
  WHERE t.name = 'Krabappel';
  

Example imdb database (11.1.2)

• also available, imdb_small with fewer records (for testing queries)
• other tables:
  • directors (id, first_name, last_name)
  • movies_directors (director_id, movie_id)
  • movies_genres (movie_id, genre)

IMDb query example

[stepp@webster ~]$ mysql -u myusername -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.

mysql> use imdb_small;
Database changed

mysql> select * from actors where first_name like '%mick%';
+--------+------------+-----------+--------+
| id     | first_name | last_name | gender |
+--------+------------+-----------+--------+
|  71699 | Mickey     | Cantwell  | M      | 
| 115652 | Mickey     | Dee       | M      | 
| 470693 | Mick       | Theo      | M      | 
| 716748 | Mickie     | McGowan   | F      | 
+--------+------------+-----------+--------+
4 rows in set (0.01 sec)

IMDb table relationships / ids (11.4.3)

Designing a query (11.4.4)

• Figure out the proper SQL queries in the following way:
  • Which table(s) contain the critical data? (FROM)
  • Which columns do I need in the result set? (SELECT)
  • How are tables connected (JOIN) and values filtered (WHERE)?
• Test on a small data set (imdb_small).
• Confirm on the real data set (imdb).
• Try out the queries first in the MySQL console.
• Write the PHP code to run those same queries.
  • Make sure to check for SQL errors at every step!!