选择没有 ROWNUM 的前 N 行?
我希望你能帮我做作业 :)
我们需要构建一个查询来输出前 N 位薪酬最高的员工。
我的版本工作得很好。
例如前 3 名:
SELECT name, salary
FROM staff
WHERE salary IN ( SELECT *
FROM ( SELECT salary
FROM staff
ORDER BY salary DESC )
WHERE ROWNUM <= 3 )
ORDER BY salary DESC
;
请注意,这将输出前 3 名且薪资相同的员工。
1:迈克,4080
2:史蒂夫,2800
2:苏珊,2800
2:杰克,2800
3:克洛伊,1400
但是现在我们的老师不允许我们使用ROWNUM
。
我四处搜寻,没有发现任何有用的东西。
我的第二个解决方案感谢 Justin Caves 的提示。
首先我尝试了这个:
SELECT name, salary, ( rank() OVER ( ORDER BY salary DESC ) ) as myorder
FROM staff
WHERE myorder <= 3
;
错误消息是:“myorder:无效标识符”
感谢 DCookie,它现在很清楚:
“[...]分析在之后应用 评估 where 子句,其中 这就是为什么你会收到 myorder 错误 是一个无效的标识符。”
包裹一个 SELECT 解决了这个问题:
SELECT *
FROM ( SELECT name, salary, rank() OVER ( ORDER BY salary DESC ) as myorder FROM staff )
WHERE myorder <= 3
;
我的老师再次罢工,不允许使用这种奇特的分析函数。
第三个解决方案来自@Justin Caves。
“如果解析函数也是 不允许,我可以选择另一个选项 想象一下——一个你永远不会想到的, 曾经,曾经真正在实践中写作, 会是这样的“
SELECT name, salary
FROM staff s1
WHERE (SELECT COUNT(*)
FROM staff s2
WHERE s1.salary < s2.salary) <= 3
I hope you can help me with my homework :)
We need to build a query that outputs the top N best paid employees.
My version works perfectly fine.
For example the top 3:
SELECT name, salary
FROM staff
WHERE salary IN ( SELECT *
FROM ( SELECT salary
FROM staff
ORDER BY salary DESC )
WHERE ROWNUM <= 3 )
ORDER BY salary DESC
;
Note that this will output employees that are in the top 3 and have the same salary, too.
1: Mike, 4080
2: Steve, 2800
2: Susan, 2800
2: Jack, 2800
3: Chloe, 1400
But now our teacher does not allow us to use ROWNUM
.
I searched far and wide and didn't find anything useable.
My second solution thanks to Justin Caves' hint.
First i tried this:
SELECT name, salary, ( rank() OVER ( ORDER BY salary DESC ) ) as myorder
FROM staff
WHERE myorder <= 3
;
The errormessage is: "myorder: invalid identifier"
Thanks to DCookie its now clear:
"[...] Analytics are applied AFTER
the where clause is evaluated, which
is why you get the error that myorder
is an invalid identifier."
Wrapping a SELECT around solves this:
SELECT *
FROM ( SELECT name, salary, rank() OVER ( ORDER BY salary DESC ) as myorder FROM staff )
WHERE myorder <= 3
;
My teacher strikes again and don't allow such exotic analytic functions.
3rd solution from @Justin Caves.
"If analytic functions are also
disallowed, the other option I could
imagine-- one that you would never,
ever, ever actually write in practice,
would be something like"
SELECT name, salary
FROM staff s1
WHERE (SELECT COUNT(*)
FROM staff s2
WHERE s1.salary < s2.salary) <= 3
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(5)
由于这是作业,因此是提示而不是答案。您将需要使用分析函数。 ROW_NUMBER、RANK 或 DENSE_RANK 可以发挥作用,具体取决于您想要如何处理关系。
如果分析函数也被禁止,我可以想象的另一种选择——一个你在实践中永远不会真正编写的选项,就像
关于性能,我不会依赖查询中的成本数字计划——这只是一个估计,通常不可能比较不同 SQL 语句的计划之间的成本。您最好查看查询实际执行的一致获取数量之类的内容,并考虑查询性能如何随着表中行数的增加而扩展。第三个选项的效率远远低于其他两个选项,因为它需要扫描 STAFF 表两次。
我没有您的 STAFF 表,因此我将使用 SCOTT 模式中的 EMP 表
分析函数解决方案实际上与 ROWNUM 解决方案一样执行 7 次一致获取
然而,COUNT(*) 解决方案实际上执行 99 次一致获取必须对表进行两次完整扫描,因此效率降低了 10 倍以上。随着表中行数的增加,它的规模会变得更糟
Since this is homework, a hint rather than an answer. You'll want to use analytic functions. ROW_NUMBER, RANK, or DENSE_RANK can work depending on how you want to handle ties.
If analytic functions are also disallowed, the other option I could imagine-- one that you would never, ever, ever actually write in practice, would be something like
With regard to performance, I wouldn't rely on the COST number from the query plan-- that's only an estimate and it is not generally possible to compare the cost between plans for different SQL statements. You're much better off looking at something like the number of consistent gets the query actually does and considering how the query performance will scale as the number of rows in the table increases. The third option is going to be radically less efficient than the other two simply because it needs to scan the STAFF table twice.
I don't have your STAFF table, so I'll use the EMP table from the SCOTT schema
The analytic function solution actually does 7 consistent gets as does the ROWNUM solution
The COUNT(*) solution, however, actually does 99 consistent gets and has to do a full scan of the table twice so it is more than 10 times less efficient. And it will scale much worse as the number of rows in the table increases
必须用另一个 select 包装该语句的原因是因为外部 select 语句将结果集限制为所需的行号。这是有关分析的有用链接。如果您单独运行内部选择,您就会明白为什么必须这样做。分析是在评估 where 子句之后应用的,这就是您收到 myorder 是无效标识符的错误的原因。
The reason you must wrap the statement with another select is because the outer select statement is the one that limits your result set to the row numbers desired. Here's a helpful link on analytics. If you run the inner select by itself you'll see why you have to do this. Analytics are applied AFTER the where clause is evaluated, which is why you get the error that myorder is an invalid identifier.
甲骨文?那么窗口函数呢?
Oracle? What about window functions?
当您使用
count(distinct)
时,同等排名的最高薪水将被视为平局排名。When you use
count(distinct <exp>)
, equal ranking top salaries will be treated as tie ranks.您可以在 Oracle 12c 中解决此问题
(FETCH FIRST 语法是 Oracle 12c 中的新语法)
You could solve this in Oracle 12c
(FETCH FIRST syntax is new with Oracle 12c)