Like, I know it really happened. I believe that. But damn if there isn't a voice in a small corner of my mind that won't stop whispering "he faked the whole thing".
Moops
You're a moron and I'm sorry for your failed upbringing.
This looks like my ex. I'm not even tryna be mean, it just does.
Hard disagree. But that's okay, we're allowed to like different kinds of games. Yours isn't any more objective than mine though. If you don't like that kind of thing, just don't play those kinds of games. It's not a threat to you if others enjoy them.
Yeah this is a reach. He's a big enough turd we really don't need to stretch this much.
What a weird little man.
That headline is a wild ride
Why would someone go about building ruins? Wouldn't you want an actual building with walls and a roof?
Yeah, I guess it's a less-used analytic function (function? I think that's the right term here).
I believe this will only accept DENSE_RANK as the ranking part of this method, which makes sense cause you want a distinct list of ranks to identify the last one. You are right though that it's possible for the record returned by the MAX() to be arbitrary if there are duplicate values in the ORDER BY field. Luckily you can usually handle for that by using multiple fields in the ORDER BY. The conditions in the query that the function operates on top of also play a roll. You can also include a PARTITION BY, but I've only needed to use that a time or two.
I think one reason I like this more is it's more readable to me. For a lot of the other analytic functions you end up using partitions and additional keywords like "ROWS BETWEEN UNBOUNDED AND ....etc." in order to break out results the way you need. With this dense_rank method I typically accomplish that using regular 'ole WHERE conditions. Of course that's gonna be pretty subjective.
Replying on in my phone now so limited in how detailed I can be. I can give better examples later if that doesn't make sense.
Edit: I think it is an Oracle thing. Analytics are one of the areas I will unapologetically use DB-specific functions. Portability be damned! Generally they've been tuned very specifically to solve a problem with the specific engine in mind. Of course that won't always be true, but that's my general thought process.
Aww dude. What a memory.
And my vote in Oklahoma.....oh fuck it who are we kidding lol. Meaningless. I still do it though.
It really is such a perfect juxtaposition of toxic vs. healthy masculinity.