Distinct

Right, let’s talk about pagination. You’ve probably done the OFFSET 100 LIMIT 10 dance a thousand times. It’s the default. It’s also a performance nightmare waiting to happen, and I’m going to show you exactly why. The problem with OFFSET is that it’s a dumb skip. The database has to read the first 100 rows, count them, and then throw them away to give you the 10 you actually want. It’s like asking a librarian to count out the first 100 books in the library, then hand you the 101st. It gets slower and more expensive the deeper you paginate. It’s absurd.

Right, so you’ve fetched some data and it looks… repetitive. Maybe you asked for a list of departments and got back 10,000 rows because you pulled it from the employees table. This is where DISTINCT waltzes in, ready to clean up the mess. It’s the SQL keyword for “get unique values,” and it does exactly what it says on the tin. But like any simple tool, it has hidden depths and a slightly more powerful, albeit quirky, cousin: DISTINCT ON. Let’s get into it.

Right, let’s talk about LIMIT and OFFSET. You’re going to use them constantly, and you’re going to hate them eventually. They are the duct tape and baling wire of pagination—it gets the job done in a pinch, but you wouldn’t want to build a skyscraper with it. They feel intuitive: “just give me 10 results, but skip the first 20.” And for small datasets, that’s perfectly fine. But the moment your data grows, this approach reveals its fundamental, almost comical, flaw.

Alright, let’s talk about ORDER BY. This is where you stop just grabbing data and start imposing some actual order on the chaos. It’s the difference between a pile of ingredients and a prepared meal. The ORDER BY clause is your way of telling the database, “I don’t just want the data; I want it like this.” The basic syntax is brain-dead simple: ORDER BY column_name. But the devil, and the real power, is in the details.

Alright, let’s talk about the WHERE clause. This is where you stop just fetching data and start interrogating it. Think of SELECT as your “grab everything” command. WHERE is the part where you say, “…but only the stuff that meets these conditions.” It’s the bouncer at the club of your database, deciding which rows get to come in and which get left out in the cold. The magic of WHERE is in its operators. They’re the vocabulary you use to describe exactly what you’re looking for.

Right, let’s talk about the part of the SELECT statement that feels the most like creative writing: the column list. This is where you tell the database exactly what you want to see, and it’s far more powerful than just listing a few column names. You can rename things on the fly, perform calculations, and even create entirely new data from what’s stored. It’s the projection of your data universe.