A personal tracker for LeetCode SQL problems β solutions, notes, and a centralized table for progress and quick reference.
- Quick Overview
- Status Legend
- Problems Tracker
- How to Add / Update an Entry
- Naming & File Structure
- Contribution Guide
- Tips
- Purpose: Keep a single, well-organized place to track SQL problems solved on LeetCode for practice and revision.
- How to use: Create a folder for each problem and add a table row summarizing the problem, topics, status, and a link to the LeetCode problem.
- β¬οΈ To Solve β Planned but not started
- π In Progress β Currently working on it
- β Solved β Completed and solution added to the repo
| # | Title | Difficulty | Topics | Status | Link | Notes |
|---|---|---|---|---|---|---|
| 1757 | Recyclable and Low Fat Products | Medium | JOIN, AGGREGATE | β | https://leetcode.com/problems/recyclable-and-low-fat-products/ | Solution folder: 1757. Recyclable and Low Fat Products |
| 1068 | Product Sales Analysis I | Medium | AGGREGATE, GROUP BY | β¬οΈ | β | Add solution when ready: 1068. Product Sales Analysis I |
| 1148 | Article Views I | Medium | WINDOW, GROUP BY | π | β | In progress β exploring window functions |
Tip: Keep the table sorted by problem number (or by status) so it's easy to scan.
- Create a folder named
NNNN. Problem Title(e.g.,1068. Product Sales Analysis I). Use 4-digit numbers to keep ordering consistent. - Add at least these files inside the folder:
solution.sqlβ the SQL solution (with comments if needed)README.mdβ short explanation of approach, edge cases, and complexity notes
- Add or update a row in the
Problems Trackertable above with the problem number, title, difficulty, topics, status, link, and any notes. - Open a PR (if contributing) with a concise description and link to the problem.
Recommended repository layout:
NNNN. Problem Title/
ββ solution.sql
ββ README.md
- Use the exact folder format
NNNN. Problem Title(keep spaces and punctuation human-readable). - Use a consistent tag set in Topics (e.g., JOIN, GROUP BY, WINDOW, AGGREGATE, FILTER).
- Feel free to open an issue or PR for new problems, fixes, or improvements.
- When opening a PR, include a short description of the approach and any noteworthy edge cases.
- If you add a new problem, update the
Problems Trackertable and include working SQL insolution.sql.
- Use consistent tags in Topics to enable quick scanning (e.g., JOIN, AGGREGATE, WINDOW).
- Put tricky queries and optimization notes in the folder
README.mdso others can learn from them.
Last updated: 2026-01-09