Honestly more readable than a lot of SQL I've read. It even has hierarchical grouping.
this post was submitted on 27 Dec 2023
484 points (96.7% liked)
Programmer Humor
23995 readers
1365 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
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)
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?
load more comments
(1 replies)
load more comments
(3 replies)
Honestly not the worst thing I’ve seen.
I actually like this. This would allow reuse of all the infrastructure we have around XML. No more SQL injection and dealing with query parameters? Sign me up!
Assuming it's built well. As someone else pointed out, it doesn't look quite right here.
Not only is this really gross, it's also straight up wrong. It's missing a from clause, and it makes no sense for a where clause to be nested under the select. The select list selects columns from rows that have already been filtered by the where clause. Same for the limit.
Also just gonna go ahead and assume the JSX parser will happily allow SQL injection attacks...
Ah yes. That's what the kids call "sqlx" right?
NGL, if it has real time code completion and compile time SQL checks, this is fine.
When you are assigned to write database queries at work and your academical background is that online react bootcamp
if you don't believe that adding more structure to the absolute maniacal catastrophe that is sql is a good thing then i'm going to start to have doubts about your authenticity as a human being
If you think this is more structured than traditional SQL, I really disagree. Is this a select * query, it's ambiguous. Also what table is being queried here there's no from or other table identifier.
load more comments
(20 replies)
Remember kids, JSX is just function calls. It can't hurt you.
Oh it can and it did.
The most offensive thing here is the amount={5} attribute. What is it? It's not XML.
It's a react component and that would be the proper way to give a numerical value in jsx
JSX has grown beyond react, so without further context it doesn't have to be react.
please kindly send all javascript into the sun and explode it
That's XML though.. not that I'm disagreeing.
Not XML. JSX. It's javascript's answer to markup.
Gross.
The worst of both worlds…
load more comments
(2 replies)
I haven't been this pissed off since LINQ started allowing syntax switches in random-ass places.
still more readable than sqlalchemy exceptions
"HTTP and the Web is a totally reliable and easy to use internet protocol"
Omg that's terrible! Link?
Is that select * ?
I expect it looks more cumbersome with joins and multiple columns from different tables.
Of course not... where's the damn tag..?
got no clue abot sql. what is wrong and how is it supposed to look like?
this basically xml being made to look like SQL. It's gross and that's why it's funny
SQL is supposed to look like this: SELECT status, name FROM some_table LIMIT 5
Different language
Sharepoint queries are written in something very similar 🤢
I still have nightmares from the one time I had to use that.
I kind of like it. I can understand where it start and end.
view more: next ›