Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Money are liquidity, therefore they float )))
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
Why did you change the table name to d (assuming this is in fact what you did)? And why is this best practices?
This comment is hidden because it contains spoiler information about the solution
I would want to see zero if there were a "name" and "id" without toys...
It depends on the question: in this instance, I feel the prompt wants a count for every name on the list.
As compared to only including names that indeed have a "toy_count" > 0.
This is certainly not the worst solution, but it isn't the best either.
It's easier for me to read your code if there are line breaks, at the very least, after commas.
In addition being explicit by using "AS" helps.
Also...where's your semi-colon?
This comment is hidden because it contains spoiler information about the solution
ive been working through all the SQL things after reading on SQL from sql bolt. this short hand is very confusing. also what do you write people P......toys t?
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
This comment is hidden because it contains spoiler information about the solution
No, you don't have to use join on a particular column. In fact, most of the solutions on here are what I would call bad practices in that they actually require data from the toys table to complete. You should really just do a count(1) so that when the join is happening underneath it could just use the index to get to the answer instead of requiring a table lookup for the value.
Agree, it must be LEFT JOIN (in case of 'people LEFT JOIN toys) when there may be people who don't have any toys. The dataset is wrong and can lead to bad solution that fits this particular dataset but not general case.
Loading more items...