Urgent.News

What's breaking now, across thousands of outlets.

Tech

How to Master Intermediate SQL in Under 10 Minutes

Most people plateau at the same point in SQL. They can write a SELECT , join two tables, and filter with WHERE . Then they hit a wall the moment a query needs to answer something slightly harder — a running total, a rank within a group, a query built from smaller pieces. That wall isn't about talent. It's about five concepts nobody explains well the first time. Learn these, and you jump from…

Mastering intermediate SQL can seem daunting, but it boils down to five key concepts that are often overlooked in beginner resources. The first concept is to stop thinking in rows and start thinking in sets. SQL operates on entire sets of data at once, so understanding this shift in mindset can help you utilize more powerful clauses like GROUP BY and window functions.

The second concept is getting comfortable with all four types of JOINs. While INNER JOIN is commonly known, it's crucial to understand LEFT, RIGHT, and FULL OUTER JOINs to handle situations where you need data that may not perfectly match between tables. The third concept is understanding the difference between WHERE and HAVING.

WHERE filters rows before grouping, while HAVING filters groups after they've been formed. Mixing these up is a common mistake that can lead to incorrect results. Lastly, mastering window functions is the turning point that sets intermediate SQL apart from beginner SQL. Window functions allow you to perform calculations across a set of rows, such as calculating a running total or comparing a row to its predecessor, without collapsing the rows into a single result.

By mastering these five concepts, beginners can quickly jump from a beginner to an intermediate SQL level.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Delivery Map Presence at Scale: A 4-State Room Lifecycle for Trusted Event Flow

Short answer: use a room lifecycle with explicit token scope, presence state, and recovery rules; pick the realtime API that makes those boundaries visible instead of hiding them in a client SDK.

  • Four-state lifecycle: authenticated, subscribed, publishing, recoverable
  • Server determines workspace access, client only renders presence and sends intent
  • Three streams maintained: authentication, subscription state, business events

How Scale Should Change the Way You Think in Tech

Most engineers learn technology by asking: “How do I make this work?” That is the right question—at the beginning. But as systems grow, it becomes the wrong question.

  • Shift focus from "how to make it work" to "what happens when it works for everyone"
  • At scale, engineers must think about system interactions, not just features
  • At large scale, failures become the norm and require proactive preparation

Allowlist Every Path a Docs Generator May Write

Generated reference docs stay trustworthy when a generator may write only restatable files under an allowlisted path. Support windows, uptime figures, and deprecation calendars belong in a second tree…

  • Generator limited to allowlisted directory paths
  • Separate tree for Windows uptime and deprecation
  • Linter flags unauthorized boundary crossings

More from Tuesday 8 September →