diff options
author | Ryan Bigg <radarlistener@gmail.com> | 2008-10-06 11:56:17 +1030 |
---|---|---|
committer | Ryan Bigg <radarlistener@gmail.com> | 2008-10-06 11:56:17 +1030 |
commit | b340337aaff5b59fdf2110207fec3e1c43f1380a (patch) | |
tree | 3e99159eb58dd173762118f3740461cb0459c23d /railties/doc/guides/activerecord | |
parent | 1f4bed7b1281bcecdf68971bb8932bac522bc260 (diff) | |
download | rails-b340337aaff5b59fdf2110207fec3e1c43f1380a.tar.gz rails-b340337aaff5b59fdf2110207fec3e1c43f1380a.tar.bz2 rails-b340337aaff5b59fdf2110207fec3e1c43f1380a.zip |
Added a small section on using conditions on tables from eager loads.
Diffstat (limited to 'railties/doc/guides/activerecord')
-rw-r--r-- | railties/doc/guides/activerecord/finders.txt | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/railties/doc/guides/activerecord/finders.txt b/railties/doc/guides/activerecord/finders.txt index b009063593..8ebb7200d5 100644 --- a/railties/doc/guides/activerecord/finders.txt +++ b/railties/doc/guides/activerecord/finders.txt @@ -230,8 +230,17 @@ An alternative (and more efficient) way to do eager loading is to use the joins [source, sql] `Client Load (0.000455) SELECT clients.* FROM clients INNER JOIN addresses ON addresses.client_id = client.id INNER JOIN mailing_addresses ON mailing_addresses.client_id = client.id + This query is more efficent, but there's a gotcha. If you have a client who does not have an address or a mailing address they will not be returned in this query at all. If you have any association as an optional association, you may want to use include rather than joins. +When using eager loading you can specify conditions for the columns of the tables inside the eager loading to get back a smaller subset. If, for example, you want to find a client and all their orders within the last two weeks you could use eager loading with conditions for this: + +[source, Ruby] + +Client.find(:first, :include => "orders", :conditions => ["orders.created_at >= ? AND orders.created_at <= ?", Time.now - 2.weeks, Time.now]) + +[source] + == Dynamic finders With every field (also known as an attribute) you define in your table, ActiveRecord provides finder methods for these. If you have a field called `name` on your Client model for example, you get `find_by_name` and `find_all_by_name` for free from ActiveRecord. If you have also have a `locked` field on the client model, you also get `find_by_locked` and `find_all_by_locked`. If you want to find both by name and locked, you can chain these finders together by simply typing and between the fields for example `Client.find_by_name_and_locked('Ryan', true)`. These finders are an excellent alternative to using the conditions option, mainly because it's shorter to type `find_by_name(params[:name])` than it is to type `find(:first, :conditions => ["name = ?", params[:name]])`. @@ -341,3 +350,6 @@ Thanks to Mike Gunderloy for his tips on creating this guide. 1. Extended conditions section to include IN and using operators inside the conditions. 2. Extended conditions section to include paragraph and example of parameter safety. 3. Added TODO sections. + +=== Monday, 06 October 2008 +1. Added section in Eager Loading about using conditions on tables that are not the model's own. |