Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Select Star SQL, an interactive SQL book

selectstarsql.com

Post reply on HN
Print view View original

81–90 of 121 posts

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

#81

Post by chris_wot »

wieghant wrote: post #76
yAnonymous wrote: post #74

Earlier quoted context omitted.

Why did you continue for 20 minutes if it disturbs you so much, little snow flake?

Why did you choose executions over something mundane like blogs or comments? Reading last statements isn't exactly something I want to be distracted by. The data is interesting sure and if this just happened to be based on something you did recently, I get it. It's not something I'd recommend to students doing data science or getting acquainted with SQL when there's less morbid source material out there. The interact…

I found it engaging, and a truly real world example of how what we do can impact others, provide us with insights we might not normally have, and can help us influence the world around us.

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

#82

Post by jyriand »

TheForumTroll wrote: post #63

Building a site for Google Chrome is like building for IE ActiveX back in the day. I'm surprised this isn't the main topic discussed here.If it doesn't work in Firefox, it isn't worth supporting. We need an open web.

It supports Firefox, you just have to enable a component from your about:config.

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

#85

Post by sqldba »

m_st wrote: post #66
dm8 wrote: 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.

It’s also how azure query language works.

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

#87

Post by baby »

rootlocus wrote: post #70

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 deep and moving, it makes this course more than just a course. I just fetched a few rows and read Beazley's last statement and I now have a great respect for the creator of this course.

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

#89

Post by dwdz »

pixelperfect wrote: post #19
AlisdairO wrote: post #16

Earlier quoted context omitted.

(self plug) pgexercises.com provides something like this. The code is open source, anyone is welcome to fork and populate with new data like this.

I learned SQL mostly by using your site, thank you for making it!

Me too! Thanks Alisdair!

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

#90

Post by techno_modus »

m_st wrote: post #66
dm8 wrote: 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 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.
Post reply on HN