0
Updating SQL
Would it, in theory, be possible to update SQL for it to allow us to write > FROM table SELECT variable instead of > SELECT variable FROM table and would that even make sense? I find it makes more sense to first name the dataset and then what you want to do with it.
10 Answers
+ 4
SQL syntax is just like that, from the beginning, and it had been standardised. We can't expect everything to be as we want them to be. Most of the times, it is necessary for us (learners) to adapt to the syntax, rather than expexting the syntax to follow our ideas.
Also syntax unifom lessen compatibility issues, anyone understanding SQL can work together with less things to worry about, in regards to syntax (there are exceptions).
+ 2
I'm not sure where you can send feedback in regards to SQL syntax, so I don't have the answer for the "would it be possible" question.
But I have to disagree with an argument that it wouldn't break backwards compatibility. Many people had learned SQL syntax the way it is, and now they all have to adapt to the new "standard". Many systems had been developed and are running production, and with this idea, a huge change is necessary. IMHO this would be BIG change because it will affect anyone who learned and uses SQL. Especially noting that the SELECT statement is used very frequently.
+ 1
That's right and I agree, but it doesn't answer the actual question. I mean, just allowing the order of the first two statements to be inverted wouldn't break readability, or backwards compatibility, or functionality of the language. All of the other statements in a query (WHERE etc.) come after these two statements and nothing really can affect them in any way.
+ 1
Imaginary middleware Taste ?
Transpile which language(s)?
+ 1
I wouldn't dare make it the new solely legal standard, but rather a new possibility. Both ways would be legal. Otherwise, clearly, backwards compatibility would break almost entirely 100% đ
+ 1
the middleware that transform a form of sql that thymaro propose back to normal sql before executed by dbms.
i mean its in the realm of possibility without breaking the current standard.
+ 1
I imagine a modified middleware here wouldn't be suitable for the general systems developed utilizing SQL, but it will satisfy proprietary systems, in regards to compatibility of course.
0
it doesnt have to be a standard. it (imaginary middleware) could work as a transpiler.
0
This middleware thing you guys are talking about, that would just be a workaround, right?
0
đŽ