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
The N+1 query problem can be forcibly prevented, but there is a possibility of false making of unnecessary eager loading instead. So, strict_loading may be fine in most cases, but in some cases it seems that user need to be careful (Handling of queries for performance issues is sensitive). Therefore, I think it's better to leave it up to well-informed application developers to take it or not because it's a case-by-case basis. That being said, strict_loading is a great feature of Rails 6.1 :-)
Just starting for discussion, I haven't dug into this deeply.
Should the styleguide recommend
config.active_record.strict_loading_by_default = true
?https://bigbinary.com/blog/rails-6-1-adds-strict_loading-to-warn-lazy-loading-associations
The text was updated successfully, but these errors were encountered: