SQL counting all rows instead of counting individual rows(SQL 计算所有行而不是计算单个行)
问题描述
我有一个从数据库请求数据的 SQL 语句.
I have a SQL statement which requests data from the database.
SELECT `ID`, `To`, `Poster`, `Content`, `Time`, ifnull(`Aura`,0) as `Aura` FROM (
SELECT * FROM (
SELECT DISTINCT * FROM messages m
INNER JOIN
(
SELECT Friend2 as Friend FROM friends WHERE Friend1 = '1'
UNION ALL
SELECT Friend1 as Friend FROM friends WHERE Friend2 = '1'
) friends ON m.Poster = friends.`Friend`
UNION ALL SELECT DISTINCT *, '1' FROM messages where `Poster`='1'
) var
LEFT JOIN
(
select `ID` as `AuraID`, `Status` as `AuraStatus`, count(*) as `Aura`
from messages_aura
) aura ON (var.Poster = aura.AuraID AND var.ID = aura.AuraStatus)
) final
GROUP BY `ID`, `Poster`
ORDER BY `Time` DESC LIMIT 10
这是我的 messages_aura
表格布局.它显示 ID
、Status
和 UserID
.
Here is my messages_aura
table layout. It shows ID
, Status
and UserID
.
这是上述语句的输出.
(上面截图中的ID
指的是下面的Poster
,上面截图中的Status
指的是ID
代码> 下面)
(The ID
from the above screenshot refers to Poster
below and the Status
from the above screenshot refers to ID
below)
该语句应为底行提供 1
的 Aura 计数,并为顶行提供 2
的 Aura 计数.怎么了?
The statement should give the bottom row a Aura count of 1
and the top row an Aura count of 2
. What's wrong?
推荐答案
您缺少 GROUP BY
,因此它会计算所有内容,而不是按某些列分组.
You're missing GROUP BY
, so it's counting everything instead of grouping by some columns.
LEFT JOIN
(
select `ID` as `AuraID`, `Status` as `AuraStatus`, count(*) as `Aura`
from messages_aura
GROUP BY AuraID, AuraStatus
) aura ON (var.Poster = aura.AuraID AND var.ID = aura.AuraStatus)
这篇关于SQL 计算所有行而不是计算单个行的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:SQL 计算所有行而不是计算单个行


- 导入具有可变标题的 Excel 文件 2021-01-01
- 如何将 SonarQube 6.7 从 MySQL 迁移到 postgresql 2022-01-01
- 如何将 Byte[] 插入 SQL Server VARBINARY 列 2021-01-01
- 更改自动增量起始编号? 2021-01-01
- 使用 Oracle PL/SQL developer 生成测试数据 2021-01-01
- 如何使用 pip 安装 Python MySQLdb 模块? 2021-01-01
- 以一个值为轴心,但将一行上的数据按另一行分组? 2022-01-01
- 在SQL中,如何为每个组选择前2行 2021-01-01
- 远程 mySQL 连接抛出“无法使用旧的不安全身份验证连接到 MySQL 4.1+"来自 XAMPP 的错误 2022-01-01
- SQL 临时表问题 2022-01-01