You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are joining on names, and then on post_num.
Yesterday in our research we were led to believe that we should INNER JOIN on the IDs, not the names as those things can be variable, and joining on ID is then a consistent way for our databases to work.
I just wanted to raise an issue because I found it a bit confusing to join in a way I had been led to believe was bad practice.
(I may even have a wrong solution! Sorry if I'm wrong, just confused).
The text was updated successfully, but these errors were encountered:
@ZooeyMiller , you're right about it being good practice to put an id in the table as a primary key, but you can still join by any column you'd like and it doesn't have to be the id.
in the seconds exercise you have to link the tables together like this:
We are joining on names, and then on post_num.
Yesterday in our research we were led to believe that we should
INNER JOIN
on the IDs, not the names as those things can be variable, and joining on ID is then a consistent way for our databases to work.I just wanted to raise an issue because I found it a bit confusing to join in a way I had been led to believe was bad practice.
(I may even have a wrong solution! Sorry if I'm wrong, just confused).
The text was updated successfully, but these errors were encountered: