MySQL tables can be joined using two different syntaxes - one that simply lists the tables to be joined and then uses a where clause to select how the join is done, and the second using an explicit join keyword. Here's an example of both syntaxes in use, linking a table of estate agents (realtors) to the houses they have currently got for sale:
select agent, town, phone, aid, agid, sid, locate, asking from agents join sales on aid = agid;
select agent, town, phone, aid, agid, sid, locate, asking from agents, sales where aid = agid;
The results produced are identical and in the case of MySQL
I understand that they both run with equal efficiency - the "where" format one being recognised by the MySQL daemon as a join and converting it across.
However, I strongly recommend that you use the join syntax.
. Here's why ...
There are two types of element in a database selection command - there are MANDATORY or RULE elements which effect the validity of the data returned and if you get them wrong, the data back is going to be just plain rubbish. For example, if you were to join a table of estate agents to houses based on the street number of the house, you might well get a result set out but it would be a complete fantasy, with agent number 12 linked to all people who happen to be selling a house at number 12 in the street. So joining tables MUST be correctly applied and is a RULE element.
By contrast, choosing the data columns you want, the order of sorting, and whether or not you want properties over 200000 pounds to be returned is an OPTIONAL or REQUEST element - although you may not get back want to want if you give your MySQL the wrong request, what you'll get back will be the answer to a question that may be validly asked.
By using a join clause, you're labelling the connection of the tables as being a RULE whereas any where clauses you apply are REQUESTs. This makes automated coding much cleaner, and automation much easier.
If you want to try out this example on your own MySQL server, you can view and save the data and MySQL commands from here (written 2005-12-01, updated 2006-06-09)
Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articlesS157 - More MySQL commands 
MySQL - LEFT JOIN and RIGHT JOIN, INNER JOIN and OUTER JOIN - (2004-12-20) 
MySQL - Optimising Selects - (2004-12-21) 
Getting a list of unique values from a MySQL column - (2005-04-14) 
Matching in MySQL - (2005-09-24) 
MySQL - a score of things to remember - (2005-11-12) 
SELECT in MySQL - choosing the rows you want - (2005-11-22) 
MySQL - an FAQ - (2005-12-03) 
An occasional chance, and reducing data to manageable levels - (2005-12-04) 
Combining similar rows from a MySQL database select - (2006-01-17) 
Giving the researcher power over database analysis - (2006-01-22) 
Saving a MySQL query results to your local disc for Excel - (2006-01-29) 
Key facts - SQL and MySQL - (2006-02-04) 
Helicopter views and tartans - (2006-04-06) 
MySQL - the order of clauses and the order of actions - (2007-06-01) 
Outputting numbers as words - MySQL with Perl or PHP - (2007-06-17) 
MySQL joins revisited - (2007-09-03) 
Joining MySQL tables revisited - finding nonmatching records, etc - (2008-03-15) 
Finding words and work boundaries (MySQL, Perl, PHP) - (2008-08-03) 
Ruby, Perl, Linux, MySQL - some training notes - (2008-11-23) 
MySQL - looking for records in one table that do NOT correspond to records in another table - (2009-03-31) 
Grouping rows for a summary report - MySQL and PHP - (2009-06-27) 
MySQL - efficiency and other topics - (2009-10-10) 
Relating tables with joins in MySQL - (2010-02-21) 
Counting rows in joined MySQL tables - (2010-02-22) 
Optimising and caching your MySQL enquiries - (2010-02-22) 
Removing duplicates from a MySQL table - (2010-02-22) 
Databases - why data is split into separate tables, and how to join them - (2010-11-20) 
SQL - Data v Metadata, and the various stages of data selection - (2011-04-29) 
Extracting data from backups to restore selected rows from MySQL tables - (2015-05-01)
Some other Articles
Open source questions? Anyone can ask.Crazy Day-siesMySQL - JOIN or WHERE to link tables correctly?Exciting futures - the Well House Manor projectDomain Forwarding - 2 ways of doing itDynamic Web presence - next generation web siteSnippets from GeekmasComment, please!