Many of us know about includes, joins but sometimes we confuse about their usage. As I was experimenting with code refactoring in one of my projects, there I have tried these things. So I thought I can share these findings with you guys. As we know includes and join are used when we are performing operations on associated tables. Both are used for the same purpose. : Uses eager loading, When we want to fetch data along with an associated table then includes must be used. Includes Uses lazy loading. We can use joins when we want to consider the data as a condition from the joined table but not using any attributes from the table. Joins: I will show you an example where includes is preferred instead of joins, also I have benchmarked both the queries so that you can see which is faster!!! < : < : , : : class Item ApplicationRecord belongs_to user end class User ApplicationRecord has_many items dependent destroy end Now I want to display the item title with the user's first name. Using includes the query output will be, puts Benchmark.measure {
items = Item.includes(:user)
items.each |item|
 item.title
 item.user.first_name
end
} do Using joins query output will be, puts Benchmark.measure {
items = Item.joins(:user)
items.each |item|
 item.title
 item.user.first_name
end
} do So it's self-explanatory, that include is preferred. But if we want to have items where user_id: 1, and we are not displaying any data from User table, then only use joins, because this will not load any user's data until we want(lazy load). As given below. items = Item.joins(:user).where(user_id: )
items.each |item|
 item.title
end 1 do Below are some reference links. You can watch them for your understanding: http://railscasts.com/episodes/181-include-vs-joins?autoplay=true

Fetch

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

Differences Between Includes and Joins in Ruby on Rails

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

ActiveRecord on MySQL— Iterating over large tables with conditions

Speed Up Allocating ActiveRecord Objects

100 Days of AI Day 1: From Newsletter to Podcast, Leveraging AI for Audio Transformation

10 Tips For Junior Developers To Succeed in Code

25 Useful Websites Developers Don't Use Enough

ActiveRecord on MySQL— Iterating over large tables with conditions

Speed Up Allocating ActiveRecord Objects

100 Days of AI Day 1: From Newsletter to Podcast, Leveraging AI for Audio Transformation

10 Tips For Junior Developers To Succeed in Code

25 Useful Websites Developers Don't Use Enough

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps