Question regarding loading relations and performance

[bookshelf]

Question regarding loading relations and performance

[tgriesser]

The library uses joins where appropriate (when doing a belongsToMany relation with an interim table) - otherwise, the query above is equivalent to:

SELECT * FROM sitesmeta
where sitesmeta.site_id =1

having the join statement doesn't really do anything there, since there's not a good way to split out all of the joined columns without requiring that the entire schema be defined in your model. Also, it uses WHERE IN when eager loading on multiple, so I'd say that this is the most efficient it's going to get without adding too much complexity. I'm also going to be doing a through method soon, that will allow for dynamic relations that uses joins and pass through another model... still finishing that up.

If you want to build a complex query, you should use the query method to add additional clauses to the current select / insert / delete statement executed on a model or collection.