News for hackers. Stuff that matters.
Re:Show HN: Select Star SQL, an interactive SQL book by m_st on Tuesday September 04, 2018 @03:59AM (#17907376)
I agree except one thing: SELECT cols FROM table. This should really be FROM table SELECT cols as every modern SQL editor will then be able to show you a list of available columns.

See LINQ. There they had the opportunity to fix it and it works just great.

Re:Show HN: Select Star SQL, an interactive SQL book by piaste on Tuesday September 04, 2018 @12:30PM (#17910262)
More generally, statements should appear in the same order as they are executed, as far as this is possible.

This nullifies some other common sources of confusion, such as which statements are executed before a GROUP BY and which ones after (and why HAVING exists as a keyword). It's also similar to how CTE syntax is generally much more readable than subqueries.

Re:Show HN: Select Star SQL, an interactive SQL book by hesk on Wednesday September 05, 2018 @05:03PM (#17921900)
The order of clauses in a SQL statement should have no relation on the order of execution because SQL is a declarative query language. The query specifies what the user wants and not how the system should compute the answer.

This declarative property also provides a (somewhat weak) motivation of why SELECT should come first. Precisely because it answers part of the WHAT, i.e., the schema of the result.

Re:Show HN: Select Star SQL, an interactive SQL book by techno_modus on Tuesday September 04, 2018 @07:55AM (#17908350)
I personally think first about the loop/iterator organization (FROM in SQL) and only after that what I am going to do with its elements.

However,

    SELECT a1,a2,... FROM Table AS t WHERE Condition
is syntactically equivalent to Python list comprehension:

    [(t.a1,t.a2,...) for t in Table if Condition]
Here the use of attributes (SELECT) is also written before the iterator.

SELECT is also analogous to normal loops:

    foreach t in Table
      if not Condition: continue
      # Use t.a1, t.a2 etc.
Here we first provide the loop specification while the usage of elements is written only in the body.
Re:Show HN: Select Star SQL, an interactive SQL book by lozzo on Tuesday September 04, 2018 @09:19AM (#17908817)
I concur. I always start with select * from table because I cannot possibly remember all the right column names
Re:Show HN: Select Star SQL, an interactive SQL book by nexxer on Wednesday September 12, 2018 @09:38AM (#17968565)
In the clients I've used (SQLYog, Mysql Workbench), aliasing a table lets you use autocomplete when referencing that alias followed by a dot.

So, I will start with a SELECT * FROM myTable t, then go back and replace * with t.<columns appear here>.

I'll use the same in other places in the query like WHERE conditions.

Re:Show HN: Select Star SQL, an interactive SQL book by jrockway on Tuesday September 04, 2018 @04:10AM (#17907421)
I mean, it works either way. Once you type the column names, it can guess the table name easily.

I use DataGrip at work and it can complete the column names without knowing the table name, so it ends up not being a problem.

Re:Show HN: Select Star SQL, an interactive SQL book by dragonwriter on Tuesday September 04, 2018 @12:48PM (#17910469)
> Once you type the column names, it can guess the table name easily.

If the query is simple enough that a natural join would work and you aren't doing FROM clause aliasing (which can be useful to make reusable queries self-documenting), sure.

For more complex queries and obviously any time table or column aliasing are used, that becomes somewhere between less likely and logically impossible.

Re:Show HN: Select Star SQL, an interactive SQL book by icc97 on Tuesday September 04, 2018 @03:49PM (#17912222)
I'd rather have the enjoyment of being able to think in normal English speak rather than Yoda speak just to fix one edge case that appeared decades after they came up with the syntax.
Re:Show HN: Select Star SQL, an interactive SQL book by sqldba on Tuesday September 04, 2018 @07:06AM (#17908118)
It’s also how azure query language works.