aboutsummaryrefslogtreecommitdiffstats
path: root/railties
diff options
context:
space:
mode:
authorJaime Iniesta <jaimeiniesta@gmail.com>2010-04-07 18:19:17 +0200
committerXavier Noria <fxn@hashref.com>2010-04-09 04:45:03 -0700
commit40e9cb6f4df3f10ef80284023595fe6a955e1740 (patch)
treef1dfa6ac6d1fc76d3356814e7205800e9e059e3e /railties
parent647addd8e022012b159bc2298c5e23b5c8ff315c (diff)
downloadrails-40e9cb6f4df3f10ef80284023595fe6a955e1740.tar.gz
rails-40e9cb6f4df3f10ef80284023595fe6a955e1740.tar.bz2
rails-40e9cb6f4df3f10ef80284023595fe6a955e1740.zip
Fixed duplicated IDs on active_record_querying guide to validate XHTML 1.0 Strict
Diffstat (limited to 'railties')
-rw-r--r--railties/guides/source/active_record_querying.textile4
1 files changed, 2 insertions, 2 deletions
diff --git a/railties/guides/source/active_record_querying.textile b/railties/guides/source/active_record_querying.textile
index a993dad900..edd8ea3640 100644
--- a/railties/guides/source/active_record_querying.textile
+++ b/railties/guides/source/active_record_querying.textile
@@ -274,7 +274,7 @@ Client.where(
This makes for clearer readability if you have a large number of variable conditions.
-h5. Range Conditions
+h5(#array-range_conditions). Range Conditions
If you're looking for a range inside of a table (for example, users created in a certain timeframe) you can use the conditions option coupled with the +IN+ SQL statement for this. If you had two dates coming in from a controller you could do something like this to look for a range:
@@ -353,7 +353,7 @@ The field name does not have to be a symbol it can also be a string:
Client.where({ 'locked' => true })
</ruby>
-h5. Range Conditions
+h5(#hash-range_conditions). Range Conditions
The good thing about this is that we can pass in a range for our fields without it generating a large query as shown in the preamble of this section.