Rank with explicit tie behavior
See this course’s project requirements
A reproducible SQLite attendance analysis with per-session rank, running totals and prior-period changes that retains every original row.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- A grouped-versus-windowed result choice.
- An independent session sequence with deterministic ordering.
- A week rank record 3,1,1 with declared tie behavior.
- Running-total rows A 8,20,32 and B 6,15.
- A row-comparison record with honest missing-baseline handling.
- A reproducible window-analysis packet.
Review and revise
Use these criteria to check your work and choose what to improve.
- The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
- Normal, boundary and rejected cases are recorded with expected versus observed results.
- The changed case has a correct explanation and does not rely on hidden state.
- The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Want more background?
The idea in everyday life
A attendance 12,12,8 ranks 1,1,3 under descending RANK. Chronological output has ranks 3,1,1.
RANK assigns peers the same rank and leaves gaps after ties. DENSE_RANK removes those gaps; ROW_NUMBER gives distinct numbers and needs a tie-breaker for a repeatable choice.
Rank with explicit tie behavior — original worked practice
RANK assigns peers the same rank and leaves gaps after ties. DENSE_RANK removes those gaps; ROW_NUMBER gives distinct numbers and needs a tie-breaker for a repeatable choice.
A attendance 12,12,8 ranks 1,1,3 under descending RANK. Chronological output has ranks 3,1,1.
1. Step 1
Sort A values descending for ranking.
You should see: 12 and 12 tie at the top.
This keeps the rule and its observable result together.
2. Step 2
Assign RANK positions.
You should see: Top tier 1,1; next position 3.
This keeps the rule and its observable result together.
3. Step 3
Compare DENSE_RANK and ROW_NUMBER conceptually.
You should see: Dense ranks 1,1,2; row numbers are three distinct positions.
This keeps the rule and its observable result together.
4. Step 4
Return ranks to the chronological rows.
You should see: A week rank record 3,1,1 with declared tie behavior.
This keeps the rule and its observable result together.
What to finish
A week rank record 3,1,1 with declared tie behavior.
Watch for this
Expecting RANK to assign different positions to equal attendee counts.
How can I tell I understand it?
Explain and demonstrate the required distinction: RANK assigns peers the same rank and leaves gaps after ties. DENSE_RANK removes those gaps; ROW_NUMBER gives distinct numbers and needs a tie-breaker for a repeatable choice. Show a changed input and the expected result without weakening this contract.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.