Home Accessibility Courses Twitter The Mouth Facebook Resources Site Map About Us Contact
Retiring, March 2020 - sorry, you have missed our final public course.
The Coronavirus situation has lead us to suspend public training - which was on the cards anyway, with no plans to resume

Please ask about private 'maintenance' training for Python, Tcl, Perl, PHP, Lua, etc
Happily continuing private consultancy / programming work
Relating tables with joins in MySQL

Relational Databases are stores of data in which that data can be matched using common characteristics. For example, I have a table of data about programming languages (which includes a columns for the name of the language and the author) and another table of data about our courses which includes the course name, and the level - beginner, intermediate or advanced. With a relational database, one of the ways I can link the tables (relate the data in them together) is via a join.

Aside - It's a good idea to keep data in separate tables as I've described in my example to avoid having to duplicate the same information many times over - that would be inefficient, and a maintenance nightmare

When you are joining tables, you tell MySQL which column in the first table is to link to which column in the second table. And you also need to decide what to do about partial records that don't match up - do you ignore them, or fill them in with nulls to make the record complete? We have a very popular tutorial [here] on this.

If you are looking for a combined table for presentation which includes unmatched ("orpan") records in both directions at the same time, you'll not be able to produce it with a single select - but rather you'll use a UNION of two selects, which you can combine into a single SQL statement. Here is an example:

(select * from dm_subjects left join dm_courses
on su_id = co_su)
(select * from dm_subjects right join dm_courses
on su_id = co_su where su_id is NULL)
order by su_name desc, co_key;

The first join selects all the records that match across the tables and the records which are orphans in the left table. The second join adds in all the records which are built from orphans in the right table.

In my example, I can now produce a combined result which shows on a single display ALL of my courses, ALL of the languages, whether of not there is a language description for the course, and whether or not we offer a course in the language.

Let's see that table:

top of sample table
bottom of sample table

You'll note numerous complete records ... and also records for the Go! and Scala programming languages on which (at the time of writing) we don't offer courses. And you'll see records for our Linux and MySQL courses, even though those are not really programming languages to don't have the extra data from the language table.

Aside - Note the difference between a NULL field and an empty one - in the example I have put an empty field against Java to demonstrate the different handling. This is another vital aside - you MUST not assume that just because you don't know how many children someone has that they have none, and in effect that's what you're doing if you confuse NULL and "".

The complete set of MySQL instructions that I used to set up this examples may be seen [here] (also includes sample joins!) and the PHP program / page which I used to present the data on the user's browser is [here]. You can run the join demonstration for yourself on our server [here] ... and of course we would welcome you on our MySQL Course here.
(written 2010-02-21, updated 2010-03-03)

Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articles
S157 - More MySQL commands
  [4481] Extracting data from backups to restore selected rows from MySQL tables - (2015-05-01)
  [3270] SQL - Data v Metadata, and the various stages of data selection - (2011-04-29)
  [3061] Databases - why data is split into separate tables, and how to join them - (2010-11-20)
  [2647] Removing duplicates from a MySQL table - (2010-02-22)
  [2645] Optimising and caching your MySQL enquiries - (2010-02-22)
  [2644] Counting rows in joined MySQL tables - (2010-02-22)
  [2448] MySQL - efficiency and other topics - (2009-10-10)
  [2259] Grouping rows for a summary report - MySQL and PHP - (2009-06-27)
  [2110] MySQL - looking for records in one table that do NOT correspond to records in another table - (2009-03-31)
  [1904] Ruby, Perl, Linux, MySQL - some training notes - (2008-11-23)
  [1735] Finding words and work boundaries (MySQL, Perl, PHP) - (2008-08-03)
  [1574] Joining MySQL tables revisited - finding nonmatching records, etc - (2008-03-15)
  [1331] MySQL joins revisited - (2007-09-03)
  [1235] Outputting numbers as words - MySQL with Perl or PHP - (2007-06-17)
  [1213] MySQL - the order of clauses and the order of actions - (2007-06-01)
  [673] Helicopter views and tartans - (2006-04-06)
  [591] Key facts - SQL and MySQL - (2006-02-04)
  [581] Saving a MySQL query results to your local disc for Excel - (2006-01-29)
  [572] Giving the researcher power over database analysis - (2006-01-22)
  [567] Combining similar rows from a MySQL database select - (2006-01-17)
  [517] An occasional chance, and reducing data to manageable levels - (2005-12-04)
  [515] MySQL - an FAQ - (2005-12-03)
  [513] MySQL - JOIN or WHERE to link tables correctly? - (2005-12-01)
  [502] SELECT in MySQL - choosing the rows you want - (2005-11-22)
  [494] MySQL - a score of things to remember - (2005-11-12)
  [449] Matching in MySQL - (2005-09-24)
  [279] Getting a list of unique values from a MySQL column - (2005-04-14)
  [159] MySQL - Optimising Selects - (2004-12-21)
  [158] MySQL - LEFT JOIN and RIGHT JOIN, INNER JOIN and OUTER JOIN - (2004-12-20)

Back to
What does a web application look like under Tomcat?
Previous and next
Horse's mouth home
Forward to
Counting rows in joined MySQL tables
Some other Articles
Compile but do not run PHP - syntax check only
Relating tables with joins in MySQL
What does a web application look like under Tomcat?
Object Oriented Programming in PHP
How is your tax pound spent?
su or su - ... what is the difference?
Finding what has changed - Linux / Unix
4759 posts, page by page
Link to page ... 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96 at 50 posts per page

This is a page archived from The Horse's Mouth at http://www.wellho.net/horse/ - the diary and writings of Graham Ellis. Every attempt was made to provide current information at the time the page was written, but things do move forward in our business - new software releases, price changes, new techniques. Please check back via our main site for current courses, prices, versions, etc - any mention of a price in "The Horse's Mouth" cannot be taken as an offer to supply at that price.

Link to Ezine home page (for reading).
Link to Blogging home page (to add comments).

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2020: 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01225 708225 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho

PAGE: http://www.wellho.net/mouth/2643_Rel ... MySQL.html • PAGE BUILT: Sat May 27 16:49:10 2017 • BUILD SYSTEM: WomanWithCat