this post was submitted on 27 Dec 2023
484 points (96.7% liked)

Programmer Humor

25594 readers
960 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Witchfire@lemmy.world 131 points 2 years ago* (last edited 2 years ago) (2 children)

Honestly more readable than a lot of SQL I've read. It even has hierarchical grouping.

[–] reimufumo@lemmy.ca 3 points 2 years ago (1 children)

true, but having it look like a component might get annoying. since this is likely to stay at the top, having an island of non components between two components might make it hard to see where functions start and end. and if this isn't used directly inside a component it'll just look dumb and inefficient (this also looks like it'll take way more to edit once you change something)

[–] bahbah23@lemmy.world 2 points 2 years ago* (last edited 2 years ago) (1 children)

I think I agree with you both. I'm not a Node developer; could you keep your SQL objects/components in a separate file so that they don't clutter up other logic?

[–] somePotato@sh.itjust.works 0 points 2 years ago* (last edited 2 years ago) (1 children)

I was disgusted by the XML at first, but it's a readable query returning a sane JSON object.

Meanwhile, I'm mantaining Java code where the SQL is a perfectly square wall of text, and some insane mofo decided the way to read the resulting list of Object[] 🤮 is getting each column by index... so I'd switch to SQXMLL in a heartbeat.

[–] blackbrook@mander.xyz 0 points 2 years ago (1 children)
[–] shotgun_crab@lemmy.world 1 points 2 years ago

JOOQ made me realize that most ORMs suck