It will probably print an error message to the terminal before exiting. But you should definitely try this today!
I apologize. There's some magic I put into our readings to say "format this code as SQL" but apparently I made a mistake in a few places and we got ugly unformatted code.
Here's how it was supposed to look select statement
Let's look at examples of queries
NULL is different from other things. So if we do
And some birthdates are NULL, they won't get selected. And the same is true if we change the greater than to less thanNo error, but as you know NULL is different from other things, so it sorts to different places. Suppose we have a "birthdate" field and we sort it from lowest (oldest person) to highest (youngest person). Suppose some people didn't fill out that field and so the database stores NULL. Those people would all sort to a section of their own (either first or last, I don't remember).
That's common. Yes, they are both filters, but HAVING filters groups. For example, suppose we have some sales data. We can group them by region. Then we can filter out groups where the total sales of the region (group) is less than some value.
We won't be using database viewers, because I want people to practice the SQL language.
I'm not sure I understand your second question.
Not sure what you mean here. WHERE is always looking at column values, such as city or state or birthdate or ...
Not sure. We'll do that today, so ask again.
For sure!