Sylvie1711/SQLQuestions

questions based on SQL that ive solved on LEETCODE and their solutions to it for personal tracking

β˜… 0Forks 0GitHub β†—Compare

README

LeetCode SQL Tracker πŸ§ΎπŸ”

A personal tracker for LeetCode SQL problems β€” solutions, notes, and a centralized table for progress and quick reference.


πŸ“‹ Table of Contents


πŸ“Œ Quick Overview

  • 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.

βœ… Status Legend

  • ⬜️ To Solve β€” Planned but not started
  • πŸ”„ In Progress β€” Currently working on it
  • βœ… Solved β€” Completed and solution added to the repo

πŸ“š Problems Tracker

# 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.


πŸ”§ How to Add / Update an Entry

  1. Create a folder named NNNN. Problem Title (e.g., 1068. Product Sales Analysis I). Use 4-digit numbers to keep ordering consistent.
  2. 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
  3. Add or update a row in the Problems Tracker table above with the problem number, title, difficulty, topics, status, link, and any notes.
  4. Open a PR (if contributing) with a concise description and link to the problem.

πŸ”§ Naming & File Structure

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).

🀝 Contribution Guide

  • 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 Tracker table and include working SQL in solution.sql.

πŸ’‘ Tips

  • Use consistent tags in Topics to enable quick scanning (e.g., JOIN, AGGREGATE, WINDOW).
  • Put tricky queries and optimization notes in the folder README.md so others can learn from them.

Last updated: 2026-01-09

Contributors

Sylvie1711

Issues