N:M Relationships
Last updated
Last updated
Create a join table and utilize it in a many-to-many relationship
Use Sequelize's helper methods to add relationships between two different models.
When creating a many to many relationship, we need to have some way of creating that relationship. With a 1:M relationship, the id of the one is attached to the many (pets.userId
in the 1:M relationship in our userapp
). What do we do when there is no 1? When everything is many, we have to have some place to put the corrosponding ids.
Enter join tables! These tables have a one to many relationship with each of the relevant tables.
Often, the naming convention is to have the join table have the names of both tables. For examples if you have products and orders, the join table will often be called ProductOrders
or product_orders
.
We will be expanding our data model in userapp
to include toys for our pets.
Check out the Sequelize BelongsToMany docs for more on all of the code and conventions covered in this lesson!
In order to associate pets to toys in a many to many fashion, you will need to update the associations on the pets and toys.
Many to many associations use the belongsToMany
sequelize method, which takes a second options pargument. Use the through
option to indicate the name of the join model (in this case, PetToy
).
In order to add a unique toy to a pet, we must first try to find or create a pet, in order to make sure it is in fact unique.
Secondly, we must attach a toy to the pet, using some built in helpers.
Some ORM has capabilities to do a bulk create on an object associations, but that kind of logic is not built in Sequelize.
Take some time to use these helper functions to add more toys and more pets!
Sequelize generates helper functions that allow you to get related items. For instance, if you wanted to find all pets that used a given toy:
You can use the addModel()
helper function to add a pet association on a toy if there are no pet associations yet.
Because this is a Many to Many association, all the logic from before can be turned around to search for all the toys of a particular pet!
NOTE: In the above code, if Ruby Tuesday doesn't have any toys, that
forEach
function will crash the nodemon server! Make sure you have error handling so your whole app doesn't shut down because one pet isn't materialistic!
Since we have a 1:M relationship between users and pets as well as a N:M relationship between pets and toys, we can get all our info through the Pet model. One of the easier ways of doing this is through the include
keyword:
Or we can use a mix of include
and helper functions to get all the toys of all the pets of a certain user!
As you can see, there are MANY (to) MANY ways to get associated data when it is needed. It's also easy to see how easy it can be to get lost in nesting hell. One way to help keep things clean is to comment the end of each section. If we take the last block of code as an example: