StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMysql joins clarifications
primarykey
Id
8153209
data
AcceptedAnswerId
8153714
AnswerCount
2
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-11-16T14:25:38.163
FavoriteCount
0
LastActivityDate
2011-11-16T18:04:06.113
LastEditDate
2011-11-16T15:28:44.417
LastEditorUserId
278470
OwnerUserId
278470
ParentId
0
PostTypeId
1
Score
0
ViewCount
121
LastEditorDisplayName
text
Body
<pre><code>SELECT * FROM left_table OUTER JOIN right_table on left_table.name = righ t_table.name; SELECT * FROM left_table FULL OUTER JOIN right_table on left_table.name = right_table.name; </code></pre> These 2 statements gives below error. Are they not valid mysql statements ? <pre><code>ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'OUTER JOIN right_table on left_table.name = right_table.name' at line 1 mysql> SELECT * FROM left_table RIGHT OUTER JOIN right_table on left_table.name = right_table.name; </code></pre> and <pre><code>mysql> SELECT * FROM left_table RIGHT JOIN right_table on left_table.name = right_table.name; </code></pre> give same result. So whats the basic use of adding OUTER in statement? I want to know what special purpose does it serve by adding OUTER in statement where as without adding it also its returning same output. ---- Update ---- Ok i give my table structure <pre><code>mysql> select * from left_table; +----+---------+ | id | name | +----+---------+ | 1 | Pirate | | 2 | money | | 5 | Ninja | | 6 | pradeep | +----+---------+ </code></pre> and <pre><code>mysql> select * from right_table; +----+-------------+ | id | name | +----+-------------+ | 1 | Rutabaga | | 2 | Pirate | | 3 | Darth Vader | | 4 | Ninja | +----+-------------+ </code></pre> I ran statements like <pre><code>mysql> SELECT * FROM left_table LEFT JOIN right_table on left_table.name = right _table.name where right_table.id is NULL; +----+---------+------+------+ | id | name | id | name | +----+---------+------+------+ | 2 | money | NULL | NULL | | 6 | pradeep | NULL | NULL | +----+---------+------+------+ </code></pre> and <pre><code>mysql> SELECT * FROM left_table LEFT OUTER JOIN right_table on left_table.name = right_table.name where right_table.id is NULL; +----+---------+------+------+ | id | name | id | name | +----+---------+------+------+ | 2 | money | NULL | NULL | | 6 | pradeep | NULL | NULL | +----+---------+------+------+ </code></pre> They still produce the same output. SO if any1 can show some statement where the results will differ. i would be able to understand it.
Tags
<mysql>
Title
Mysql joins clarifications
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USHacker
UserOwnerUserId
1. USHacker
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POMysql joins clarifications
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTClose
2. VO
 singulars
 PostPostId
 POMysql joins clarifications
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTClose
CommentsPostId

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.