Following, Friending, and Lending: Self-Referential Associations with Rails
Copied from its original on lindsey.international
Self-Referential Associations happen when you connect a table back into itself in Active Record. This is commonly found in a Following function, where one User follows another. As a new Rails developer, the first time I tried these was somewhat daunting, but I managed to pull off both Following and Lending in my app. I used a helpful Rails Cast and various Google searches to figure this out.
This post assumes that you have already setup authentication in your app and have some way of referencing the logged in user (referred to as “current_user”). I have my Solution and a Starter in this github repo, both have authentication that only requires the username to login.
Start by thinking about what your associations–what are you connecting? For basic Following (in the manner of Twitter’s following feature), you are just connecting two users. Therefore, you need a join table with has_many through in your model.
Setup the join table:
Here you reference one user, but then need a way to reference a second user without interference. In this case, I use “followed” to refer to the other user–they’re the ones being followed.
You do not need to touch the Users table, since we’re using a join table. Then migrate this new table to add it to your database.
Now that you have the table, you should set up the route:
That’s it. You can nest it with users if you’d like, and then change the rest of the code to suit.
Next setup the Follow model. This is where we show that the “followed” is actually a User:
In the User model, we also need to setup associations. Since we have two users in everything we do, we need two sets of references here. The user has many follows (for the follow table) and has many followed through follows (they can follow many users). But they also can be followed. Here I used “inverse” to show the second relationship, which seemed to be the way others online were solving this issue.
So: A user has many entries in the follows table, which connect them to the people they followed. A user also has many entries in the follows table of people who are their followers.
This is a good time to setup a Follows controller, as well, with an empty class.
Since this is a self-referential association with Users, I put the actual method for following in the Users model.
This is a method called “follow” which takes in other_user (a variable I’ll be defining in the controller) and after checking to make sure they’re not already following that person, I create an entry in the follows table referencing the user the current user wants to follow.
Now I go back to the Follows controller and set up the create method. We don’t need “new” because we’re not using any views.
This takes the params and sends it to the follow method (@user becomes other_user). If the follow method works (if the user isn’t already following them), they are given an announcement saying they followed them and then redirected to their own page. If it doesn’t work, they are given an error and redirected.
Since people should be able to unfollow, as well, you set up a destroy:
Basically, you’re just destroying the entry in the follows table associated with that id.
Now for another difficult part, the views. This is where the links will go that allow users to follow each other. This can be hard to visualize how it’s supposed to happen, if you’re not using a specific follow view.
In the Users index, I put a list of the Users:
In the Users show page, I put a list of each user’s followeds and followers.
Other things you can do: Create friendships, where relationships have to be mutual to show up, or create lending features, where you connect another model and have one user lend something they own to another. For an example, check out what I did with Loans in this project.