Live data from Hacker News

Show HN: Select Star SQL, an interactive SQL book

selectstarsql.com

111–120 of 121 posts

Re: Show HN: Select Star SQL, an interactive SQL book

#111

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.

it's data that asks to be investigated. There is no reason to query meaningless data. A query that tells you something you didn't know is infinitely more useful than a query that tells you what you already knew, and a dataset that encourages you to ask your own questions and craft your own queries is infinitely more effective than, say, an imaginary book catalog or some other nonsense that doesn't at all tempt the student to ask more questions of the data.

and besides: technology is a facet of society, it is not a purely rationalist act.

Re: Show HN: Select Star SQL, an interactive SQL book

#112

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?

This breaks the site guidelines. You unfortunately have a history of posting uncivilly to HN. If you would please review https://news.ycombinator.com/newsguidelines.html and follow the rules when posting here, we'd appreciate it. The idea here is: if you have a substantive point to make, to make it thoughtfully; and if you don't, to not comment until you do.

Re: Show HN: Select Star SQL, an interactive SQL book

#114
post #66
post #11

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.

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

#115
post #33
post #31

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.

Doesn't work on Chrome for me - Version 67.0.3

Re: Show HN: Select Star SQL, an interactive SQL book

#116
i need some help im at at point were im bout go all in / cause i reall dont know what to do but i need it iv beensiging up for school an online jobs an stuff but i got a call last night an for a grant froma survay i summitted /what he called a citizens demographic survey as he called it from Washington dc for enough to get me through I'm just scared cause I know how scammers work what would u do and he has a lot of my information already check-in to make sure it was me like a legit businessman i talked with him almost a hour an can call him right know if needed ....the catch i cant i got pay 250 / because of the taxes of the transaction? help !!!!!!

Re: Show HN: Select Star SQL, an interactive SQL book

#118
post #107
post #66

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.

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

#119

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.

I like the death penalty database, it makes things so much more interesting and memorable. Data doesn't have to be boring

Re: Show HN: Select Star SQL, an interactive SQL book

#120
As someone who has never really touched SQL except very briefly during a degree module, which basically taught me nothing, I enjoyed this. I think it taught me some good stuff. I will need to go back through it as I didn't pick it all up.

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.

Post reply on HN