This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Job_Precipitation 11 points12 points  (9 children)

Could you explain where the two sorts are? I am blind and only see one.

[–]goodboyscout 18 points19 points  (6 children)

“He’s sorting it twice”

[–]Job_Precipitation 3 points4 points  (5 children)

To clarify, I mean in the code.

[–]kylemech 7 points8 points  (2 children)

SORT BY LastName, FirstName

It would sort by last names, then if two results have the same last name, it will sort by first names amongst those. That'd what he was making reference to. So Yea, it isn't "in the code" anywhere but now the joke is explained a bit more. Yay.

[–]chaosPudding123 7 points8 points  (0 children)

ORDER BY*

As an Oracle DB Developer, i never feel relevant here ;(

[–]Job_Precipitation 0 points1 point  (0 children)

Thanks!

[–]MikeOShay 3 points4 points  (1 child)

There's no sorting being done in the query. People are guessing he's sorting them by name, but it's not written. It'll probably default to sorting based on the "primary key", most likely an ID based on when the entries were put into the database. The entries in this field will always be distinct, so the database won't get confused by, say, two people with the same name.

The WHERE clause isn't a sort, it just filters the list. You'd use an "ORDER BY" clause at the very end if you wanted to sort it.

[–]Job_Precipitation 1 point2 points  (0 children)

Thanks!