Why did you use death sentence cases as data? I've spent around 20 minutes just reading the last words of various executed people. It's... disturbing and distracting.
and besides: technology is a facet of society, it is not a purely rationalist act.
111–120 of 121 posts
Why did you use death sentence cases as data? I've spent around 20 minutes just reading the last words of various executed people. It's... disturbing and distracting.
and besides: technology is a facet of society, it is not a purely rationalist act.
Why did you use death sentence cases as data? I've spent around 20 minutes just reading the last words of various executed people. It's... disturbing and distracting.
Why did you continue for 20 minutes if it disturbs you so much, little snow flake?
Congratulations! I love this kind of interactive tutorials as their helping more and more people learning stuff without a boring book and no exercises. That said: Doesn't work in Firefox and Edge? Common, are we back in 1998? Sorry for the rant, but please don't do that.
This is good intiative. We need to simplify pedagogy. On a related note, I always found the syntax of SQL to be great. Someone told me that simplicity of SQL made relational databases even more popular. It is one of the best designed language where even someone new to the field won't feel intimidated. I'm surprised designers of SQL haven't won the Turing Award yet.
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.
Earlier quoted context omitted.
https://selectstarsql.com/frontmatter.html Scroll down to Dataset. After "I’ve prepared for this book:" There is a little interactive code editor you can type in and run the query.
I was confused too. It appears the page does not work on Firefox. I get a "customElements is not defined" error in the console in Firefox and none of the interactive sections render. The page works fine on Chrome.
Earlier quoted context omitted.
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.
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.
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.
The choice of example database (the death penalty) is terrific. So much more interesting, important and compelling than the usual tired customer/product examples. I'm tired of seeing the implicit assumption around the place that software is just about business. Software should be about more than that.
That said, as a novice, the challenge questions are not in anyway suitable for a beginner. I wouldn't, and didn't, have any idea how to do them; or know where to look to find a starting point. The previous chapters do not prepare you for the challenges and I came away thinking I was useless until I click the solutions and realised there was no way I would realistically ever been able to solve them without some form of further training in SQL.