SQL Language Debate
The cluster centers on debates about SQL's strengths as a concise and powerful declarative query language versus its criticisms regarding syntax, abstractions, composability, and calls for better alternatives.
Activity Over Time
Top Contributors
Keywords
Sample Comments
SQL is way better at what it does then regular programming languages. Writing queries with SQL is much more succinct.
The problem with SQL is the language, not the paradigm.
Another .01 baked suggestion to replace SQL. SQL hasn't been replaced because it is quite concise compared to the alternatives and very powerful. Most programmers dont like it because it is not easy to get your head around it, but it is worth the effort if you can. The problem for most people is that it is a declarative language and not a procedural one.
Wasn't part of the whole premise of SQL that it is already basically natural language?
SQL is syntactic sugar for first order logic. It is much easier to query relational database with SQL than abstracting relations with ORM.
SQL is a declarative language. If you ask it for an address, it'll give you an address. Not sure what you're trying to say with that xkcd.SQL is a real language. It is testable and reusable. It's a DSL, so the syntax isn't something you have to look at most of the time unless you're a DBA. That said, not everyone hates the syntax.You're probably losing efficiency in your quest for functional paradigm perfection.
SQL seems to be the QWERTY of the data query world. It's far too entrenched.
Do you love SQL, or do you love relational algebra? Because actual SQL, the language, is pretty shitty.Perhaps the best querying language I've ever used is Q-SQL, integrated into kdb+/q. Unlike SQL, it's actually part of the language (q/k) and, most importantly, it's modular and more expressive than SQL.If you're interested in how we can do a lot better than sending strings to remote databases using an inexpressive and non-turing complete language, check it ou
Agreed that LLMs are quite good at SQL (and relational algebra). However, ask yourself this: how many programming languages do you know to at least a comfortable level? If N > 1, why not add another (SQL)? Itβs not a difficult language, which is in part why LLMs are so good at it β itβs easy to predict the next token, because there are so few of them.
Having used (a lot) of Hive SQL, I absolutely do need your query language. SQL is fundamentally incapable of expressing any sort of abstraction, so non-trivial queries quickly become completely incomprehensible, unmaintainable and bug-prone.Learning a new language is a one-time, up-front cost. Dealing with an awkward, inexpressive query language that integrates poorly with my main language, my types or my interface description languages is an ongoing source of painful friction. Learnin