News for hackers. Stuff that matters.

A comment on I don't want to learn your query language (2018). Parent comment

Re:I don't want to learn your query language (2018) by workingworkguy on Wednesday March 10, 2021 @10:10AM (#26411996)
I'm one of the analysts causing issues for the OP, but a common example to me of something that's cake in a "real" language and frustrating in sql (ms in my case) is expanding a function to take a dynamic amount of params.

myFun param =

    for each param do...
Something like that has given me WAY more headaches than i ever expected, and that's before i saw vendor code (for systems that are used by millions) handling business logic in the stored proc with a 70 case switch statement...
[ Parent | on HN ]
Re:I don't want to learn your query language (2018) by hobs on Wednesday March 10, 2021 @10:35AM (#26412301)
That's what adhoc/dynamic SQL is for if you must, and power it with another language - you are trying to loops in a set based language, its the opposite of what its good at.
[ Parent | on HN ]
Re:I don't want to learn your query language (2018) by megagator on Wednesday March 10, 2021 @10:21AM (#26412134)
Databases are generally better at storing data, not logic.
[ Parent | on HN ]
Re:I don't want to learn your query language (2018) by pwinnski on Wednesday March 10, 2021 @10:57AM (#26412549)
That sounds like switch abuse, but a better-written query builder seems like a good solution here. Use `for each param` to build a SQL query, and you're golden.
[ Parent | on HN ]