Programmer Humor

32023 readers

993 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

[email protected]

1740

I love it when I have to scream at a computer (lemmy.world)

submitted 11 months ago by tsuica to c/[email protected]

170 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 18 points 11 months ago* (last edited 11 months ago) (3 children)

Sorry, to clarify, not everything is in all caps. I'll append my prefered syntax below

WITH foo AS (
    SELECT id, baz.binid
    FROM
            bar
        JOIN baz
            ON bar.id = baz.barid
)
SELECT bin.name, bin.id AS binid
FROM
        foo
    JOIN bin
        foo.binid = bin.id

The above is some dirt simple SQL, when you get into report construction things get very complicated and it pays off to make sure the simple stuff is expressive.

[–] NedDasty 14 points 11 months ago (2 children)

You indent your JOIN? Why on earth? It lives in the same context as the SELECT.

[–] [email protected] 9 points 11 months ago

I've seen both approaches and I think they're both quite reasonable. An indented join is my preference since it makes sub queries more logically indented... but our coding standards allow either approach. We've even got a few people that like

FROM foo
JOIN bar ON foo.id = bar.fooid
JOIN baz ON bar.id = baz.barid

[–] callcc 6 points 11 months ago (1 children)

Actually not. It's part of the FROM

[–] [email protected] 2 points 11 months ago

That double indented from is hurting me

[–] Cold_Brew_Enema 1 points 11 months ago (1 children)

Um you forgot the semicolon before with assuming there isn't one in the previous statement. Syntax error. Code review failed

[–] [email protected] 5 points 11 months ago

There's no way we're running in multi statement mode... I like my prepared queries, thank you very much.