Honestly more readable than a lot of SQL I've read. It even has hierarchical grouping.
this post was submitted on 27 Dec 2023
540 points (96.9% liked)
Programmer Humor
19623 readers
65 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 1 year ago
MODERATORS
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.
React basically figured out how to make XML work.
Remember, XML was actually designed for use cases like this, thatโs why it came with XPath and XSLT, which let you make it executable in a sense by performing arbitrary transformations on an XML tree.
Back in the day, at my first coding job, we had an entire program that had a massive data model encoded in XML, and we used a bunch of XSL to programmatically convert that into Java objects, SQL queries, and HTML forms. Actually worked fairly well, except of course that XSL was an awful language to do that all in.
React simply figured out how to use JavaScript as the transformation language instead.
load more comments
(3 replies)
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)
load more comments
(2 replies)
load more comments
(1 replies)
Honestly not the worst thing Iโve seen.
I'd like you to think for a moment about CTEs, the HAVING clause, window functions and every other funky and useful thing you can do in SQL ... Now just think, do you think that this syntax supports all those correctly?
sql syntax doesn't support even itself correctly i fail to see your point
Probably no better or worse than any other ORM written in a more traditional language. Worst comes to worst, you can always escape to plain SQL.
load more comments
(1 replies)
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.
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...
load more comments
(3 replies)
I want to hate this. I really do. But the problem isโฆ I think I like it.
But how do I know if the WHERE clause is AND or OR?
We can say default is and and add an Or node for or. Similar to SoP notation, you only write +.
load more comments
(1 replies)
load more comments
(1 replies)
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.
It's JSX. It's used to embed markup into javascript
It's to embed Javascript into embedded markup in Javascript
still more readable than sqlalchemy exceptions
I haven't been this pissed off since LINQ started allowing syntax switches in random-ass places.
Omg that's terrible! Link?
"HTTP and the Web is a totally reliable and easy to use internet protocol"
Is that select * ?
I expect it looks more cumbersome with joins and multiple columns from different tables.
load more comments
(1 replies)
Joins must be a pain in the ass with hooks
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 run on the server to communicate with a database. The screenshot is jsx, which is a front-end, UI templating language. Writing SQL this way is cursed
load more comments
(2 replies)
SQL is supposed to look like this: SELECT status, name FROM some_table LIMIT 5
load more comments
(1 replies)
Of course not... where's the damn tag..?
view more: next โบ