假如行使了外毗连(LEFT,RIGHT,FULL),主表(保存表)中的不切合ON前提的列也会被插手到VT1-J2中,作为外部行,天生假造表VT1-J3。
- mysql> SELECT
- -> *
- -> FROM
- -> table1 AS a
- -> LEFT OUTER JOIN table2 AS b ON a.uid = b.uid;
- +-----+------+------+------+
- | uid | name | oid | uid |
- +-----+------+------+------+
- | aaa | mike | 1 | aaa |
- | aaa | mike | 2 | aaa |
- | bbb | jack | 3 | bbb |
- | bbb | jack | 4 | bbb |
- | bbb | jack | 5 | bbb |
- | ccc | mike | 6 | ccc |
- | ddd | mike | NULL | NULL |
- +-----+------+------+------+
- 7 rows in set (0.00 sec)
下面从网上找到一张很形象的关于‘SQL JOINS'的表明图,如若加害了你的权益,请劳烦奉告删除,感谢。
2、WHERE
对VT1进程中天生的姑且表举办过滤,满意WHERE子句的列被插入到VT2表中。
留意:
此时由于分组,不能行使聚合运算;也不能行使SELECT中建设的别名;
与ON的区别:
假若有外部列,ON针对过滤的是关联表,主表(保存表)会返回全部的列;
假如没有添加外部列,两者的结果是一样的;
应用:
对主表的过滤应该放在WHERE;
对付关联表,先前提查询后毗连则用ON,先毗连后前提查询则用WHERE;
- mysql> SELECT
- -> *
- -> FROM
- -> table1 AS a
- -> LEFT OUTER JOIN table2 AS b ON a.uid = b.uid
- -> WHERE
- -> a. NAME = 'mike';
- +-----+------+------+------+
- | uid | name | oid | uid |
- +-----+------+------+------+
- | aaa | mike | 1 | aaa |
- | aaa | mike | 2 | aaa |
- | ccc | mike | 6 | ccc |
- | ddd | mike | NULL | NULL |
- +-----+------+------+------+
- 4 rows in set (0.00 sec)
3、GROUP BY
这个子句会把VT2中天生的表凭证GROUP BY中的罗列办分组。天生VT3表。
留意:
厥后处理赏罚进程的语句,如SELECT,HAVING,所用到的列必需包括在GROUP BY中,对付没有呈现的,得用聚合函数;
缘故起因:
GROUP BY改变了对表的引用,将其转换为新的引用方法,可以或许对其举办下一级逻辑操纵的列会镌汰;
我的领略是:
按照分组字段,将具有沟通分组字段的记录合并成一笔记录,由于每一个分组只能返回一笔记录,除非是被过滤掉了,而不在分组字段内里的字段也许会有多个值,多个值是无法放进一笔记录的,以是必需通过聚合函数将这些具有多值的列转换成单值;
- mysql> SELECT
- -> *
- -> FROM
- -> table1 AS a
- -> LEFT OUTER JOIN table2 AS b ON a.uid = b.uid
- -> WHERE
- -> a. NAME = 'mike'
- -> GROUP BY
- -> a.uid;
- +-----+------+------+------+
- | uid | name | oid | uid |
- +-----+------+------+------+
- | aaa | mike | 1 | aaa |
- | ccc | mike | 6 | ccc |
- | ddd | mike | NULL | NULL |
- +-----+------+------+------+
- 3 rows in set (0.00 sec)
4、HAVING (编辑:湖南网)
【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容!
|