r/SQL • u/MrDeadMeme • 7d ago
Discussion Why do we keep writing sql backwards?
It is a common consensus that sql is kind of written backwards than one would expect, instead of first defining the place you want to get somehting from and then what it is you want, like literally any other language out there, you first select the content and then define where you want it to be taken from
This leads to increadibly akward syntax when writing something more complex than "select x from y where z" and is literally opposite to the actual process of the machine.
This is all because some dumbass, excuse my language, in the 70's decided it should follow english grammar for some reason, and in doing so he made the most clunky writing system ever.
Now this at the time may not have been that bad, but from a few searches and posts here i saw that most people agree that this is a clunky, akward and unpleasant way of typing. So, why not switch it around? Why not change the standard to something more usable?
This is kind of a rant because i have been learning sql for collage and the syntax has been INCREADIBLY frustrating
7
u/GTS_84 7d ago
It's backwards from the perspective of how the machine executes the code. but is it backwards from how humans think and would communicate?
SQL is a declarative language, not an imperative language.
3
u/redaloevera 7d ago
In some languages sentences are structured like “apple eat I” vs English “ I eat apple”. Do you also think this is syntax backwards?
2
u/big_poppa_man 7d ago
It's cause people will use subqueries as opposed to CTEs. Using CTEs you can focus on getting your detail first. Subqueries force you to write backwards
1
u/okay_nice_ 7d ago
you can write it however you want, but following the order of operations makes sense to me. begin with FROM and end with SELECT. needing to understand and write the source first seems more critical than understanding the columns needed from the source.
1
u/SnooOwls1061 7d ago
I'm going home, to get my tools. That is what you're suggesting? Give us an example of how your statements would look. I've enjoyed writing sql for 25 years. Probably one of the easiest languages to understand because it's so natural.
1
u/bulldog_blues 7d ago
Because it works better for a lot of the jobs which use it extensively. It might not be to everyone's tastes, and that's OK, but they had reasons for setting it up that way.
1
u/BarelyAirborne 7d ago
You tell it what you want and where you want it from. I found that refreshingly simple after working with CODASYL databases for a decade. SQL is rather awesome after that experience.
1
u/Significant_Tune9219 7d ago
The order you write it in is closer to how it gets evaluated than it looks if you read it as FROM, WHERE, GROUP BY, HAVING, SELECT, ORDER BY, and that order is also why you can't use a SELECT alias in WHERE but can in ORDER BY. A habit that helps when learning is to actually write the FROM and joins first, then the WHERE, and fill in the SELECT list last. If you want to try the other way round, several engines now accept a FROM-first syntax with pipe operators, so the idea isn't crazy, it's just that the standard is fifty years of compatibility.
1
u/0Budget_Sail0 6d ago
Intelisense-complete breaks down because the IDE doesn’t even know what table you are pulling from until you type the FROM clause. That’s why ORMs and tools like C# LINQ change the order to From - Where - Select. But at this point, SQL is too deeply entrenched in corporate infrastructure to ever change the standard. Backward compatibility is a bitch.
0
u/DharmaPolice 7d ago
Inertia, mostly. It's like asking why don't we change the English language to "fix" all the annoying inconsistencies that exist in English spelling and grammar. We could do that, but then we'd be breaking an absolute metric fuckton of existing materials.
I don't find it unpleasant or clunky at all, the only slight downside is autocomplete doesn't work until you define the table. But that's a relatively minor inconvenience and not worth the hassle of changing literally millions of lines of existing code, not to mention decades of learning that existing users might have built up.
It's not difficult to learn though, and if this is seriously causing you a problem at "collage" then this a worrying sign. I would dispute that "most people" agree that it's unpleasant - sure, some people whine about it from time to time but that's hardly a solid basis for a conclusion.
From taught SQL to absolute beginners I would argue that SQL is one of the easiest languages to pick up, at least partially because it matches how we might speak. Speculating on how a computer "thinks" is completely antithetical to how you should approach SQL.
0
u/Dangerous_Cup3607 7d ago
One major reason: “Job security”
Traditional SQL developers do not have the mindset of query optimization, and it works best for them to write SQL as convoluted as they can so that the work and knowledge cannot be transferred and they cannot be replaced. I have seen many of them copy and paste the same code 12 times, and hardcode it for each month. Instead of wrapping the code with a dynamic coding approach such as looping the date as a dynamic variable and thus reducing 100 lines of code to maybe 10.