Projects SQL Workspace Python Lab Leaderboard Community Conference For Companies

Home
Projects
Community

Loading the community board…

Loading…

Practise. Analyse. Build. Showcase.

Master Excel, SQL, Power BI and Python through real-world projects, guided practice, browser-based tools and mentor feedback.

A hands-on learning platform by Data Science East Africa, built to help Africa's data community learn, create and grow with confidence.

Practise

Project library
SQL workspace
Python lab
Excel projects
Power BI projects
Python projects

Progress

Your dashboard
Leaderboard
Portfolios
Pricing
User guide
Account settings

Community

Community board
Conference
For companies
About DSEAfrica
GitHub
LinkedIn
Writing on Medium
YouTube

Docs
About
@DSEAfrica
Contact

Loading the community board…

when using row_number we ignore the engineer who had the same pay as the 3rd....so there are supposed to be 4 enginee… · DSEAfrica Data Lab

Community

Felix Ng'ang'a@felix-ng-ang-a30 Sept

General

when using row_number we ignore the engineer who had the same pay as the 3rd....so there are supposed to be 4 enginee…

when using row_number we ignore the engineer who had the same pay as the 3rd....so there are supposed to be 4 engineers who are top 3 but when we use dense rank we don't ignore that hence returning an error as shown....so which is the way

1 up · 0 down · 1 reply

1 reply

LuxDevHQ Admin@luxdevhqadmin15 Oct
Hello Francids the reasoning about DENSE_RANK is right as it keeps both people who tie, which is why you get 25 rows. This question asks for exactly three per department using ROW_NUMBER, breaking ties by full_name, so the fourth engineer on 498,000 is intentionally left out. If a question ever says "everyone in the top three salaries", DENSE_RANK would be the correct choice.
0