I am doing it with subquery
I agree that your version is cleaner and easier to remember,
but you might want to add .distinct after joins to avoid duplicated authors.
Ah yes, great points! I like that as a subquery and definitely need the distinct for my example as well.
Well, this is useful, but ugly... Thinking about querying, im not supposed to "merge" anything. IMHO
My wish was Author.books.scope(:available), lol
Well you can do Author.books.available because that's just querying Book.where(author_id: X).available. But obviously this is for the more complex joining tables case, so at least you're working with the models like you normally would. Not the best, but it saves you from duplication.
The difference is that Author.books.available will return books, but Author.joins(:books).merge(Book.available) will return authors. Using merge is useful when your desired record set has conditions that are dependant on another table. As stated in the video, you're looking for **Authors** with available books, not available **books**.