The 365 Data Science team is proud to invite you to our own community forum. A very well built system to support your queries, questions and give the chance to show your knowledge and help others in their path of becoming Data Science specialists.
Ask
Anybody can ask a question
Answer
Anybody can answer
Vote
The best answers are voted up and moderated by our team

question with the the part of SQL+tableau in chart 2

question with the the part of SQL+tableau in chart 2

Super Learner
0
Votes
1
Answer


at first we select the ‘d.dept_name’
but group by ‘d.detp_no’
 
here I do not very understand well. why we don’t group by ‘d.dept_name’ then equals to the part of select?

1 Answer

365 Team
0
Votes

Hi Yanhao!
Thanks for reaching out.
I am sorry to have missed answering your question earlier. Please accept my apologies for the delayed response. 
The reason is sticking to best practices. In this example, the primary key of t_departments is the dept_no column, not dept_name
The idea is that theoretically, the same department names may have been used for different department numbers (although this is not logical, is highly unlikely, and is not what what happens in the t_employees database, it might happen by mistake and our code can be prepared for sorting the problem in such a scenario). That’s why GROUP BY the primary key column , which is dept_no.
To prove this, please feel free to refer to the DDL tab of the t_departments table.

CREATE TABLE `t_departments` (
`dept_no` char(4) NOT NULL,
`dept_name` varchar(40) NOT NULL,
PRIMARY KEY (`dept_no`),
UNIQUE KEY `dept_name` (`dept_name`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

Hope this helps.
Best,
Martin

×
Online Data Science Training
SAVE 60%