Permalink
Browse files

AR queying guide: let limit and offset be different numbers to help m…

…aking clear what is what in the explanation, rewords also a bit
  • Loading branch information...
1 parent 438bff6 commit 59945678393b591e263cdee90a8e278a723f93df @fxn fxn committed Jul 14, 2010
Showing with 6 additions and 6 deletions.
  1. +6 −6 railties/guides/source/active_record_querying.textile
@@ -447,28 +447,28 @@ h4. Limit and Offset
To apply +LIMIT+ to the SQL fired by the +Model.find+, you can specify the +LIMIT+ using +limit+ and +offset+ methods on the relation.
-You can use +limit+ to specify the number of records to be retrieved, and use +offset+ to specify the number of records to skip before starting to return the records. For example:
+You can use +limit+ to specify the number of records to be retrieved, and use +offset+ to specify the number of records to skip before starting to return the records. For example
<ruby>
Client.limit(5)
</ruby>
-This code will return a maximum of 5 clients and because it specifies no offset it will return the first 5 clients in the table. The SQL it executes will look like this:
+will return a maximum of 5 clients and because it specifies no offset it will return the first 5 in the table. The SQL it executes looks like this:
<sql>
SELECT * FROM clients LIMIT 5
</sql>
-Or chaining both +limit+ and +offset+:
+Adding +offset+ to that
<ruby>
-Client.limit(5).offset(5)
+Client.limit(5).offset(30)
</ruby>
-This code will return a maximum of 5 clients beginning with the 6th client in the clients table, skipping the first five clients as specified by the offset. The SQL looks like:
+will return instead a maximum of 5 clients beginning with the 31st. The SQL looks like:
<sql>
-SELECT * FROM clients LIMIT 5, 5
+SELECT * FROM clients LIMIT 5, 30
</sql>
h4. Group

0 comments on commit 5994567

Please sign in to comment.