AR::Relation's with eager loading cache_key's

[swalkinshaw]

Came across this gem from a Rails issue and had a similar problem I was going to solve. Thought it might be useful to include the solution in this gem as well.

We know that using includes to eager load associations is a good way to avoid N+1 queries. And obviously using fragment caching is good as well but they don't place nicely together. When fragment caching a relation that includes associations, they will all get loaded in the query to determine the cache key. In my opinion, the included associations should be discarded in this case.

If you're interested in this feature I could give it a go.

[cmer]

Would like to see your implementation of this.

On 2013-02-28, at 3:23 PM, Scott Walkinshaw notifications@github.com wrote:

Came across this gem from a Rails issue and had a similar problem I was going to solve. Thought it might be useful to include the solution in this gem as well.

We know that using includes to eager load associations is a good way to avoid N+1 queries. And obviously using fragment caching is good as well but they don't place nicely together. When fragment caching a relation that includes associations, they will all get loaded in the query to determine the cache key. In my opinion, the included associations should be discarded in this case.

If you're interested in this feature I could give it a go.

—
Reply to this email directly or view it on GitHub.

[aaronchi]

+1

[joaohornburg]

👍