3 ms·
Leading with a description of what you'll "return" makes some sense, especially when you're chaining, nesting, or otherwise combining queries. I agree that it'
by handrous 5y ago
Leading with a description of what you'll "return" makes some sense, especially when you're chaining, nesting, or otherwise combining queries.
I agree that it's kinda weird, though. Every time I need to spend serious time in SQL I end up having to re-learn how to think "inside out", for that and other reasons.
- 29athrowaway 5y agoFrom a parsing perspective, you can use the first keyword to branch to the proper parsing expression with ease... e.g.: If the query starts with "SELECT" I can use the SELECT parser. If it starts with "UPDATE" I can use the UPDATE parser and so on. With FROM/WHERE/SELECT you can no longer do that. So there's a cost... but to be honest, it's worth it in my opinion.