Changeset 4666
- Timestamp:
- 07/18/07 18:16:22 (1 year ago)
- Files:
-
- doc/branches/1.0/book/08-Inside-the-Model-Layer.txt (modified) (1 diff)
- doc/branches/1.0/book/18-Performance.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
doc/branches/1.0/book/08-Inside-the-Model-Layer.txt
r3607 r4666 406 406 407 407 >**TIP** 408 >When a `doSelect()` query returns a large number of results, you might want to display only a subset of it in your response. Symfony provides a pager class called sfPropelPager, which automates the pagination of results. Check the API documentation at [http://www.symfony-project.com/api/symfony.html](http://www.symfony-project.com/api/symfony.html) for more information and usage examples.408 >When a `doSelect()` query returns a large number of results, you might want to display only a subset of it in your response. Symfony provides a pager class called sfPropelPager, which automates the pagination of results. Check the pager documentation at [http://www.symfony-project.com/cookbook/trunk/pager](http://www.symfony-project.com/cookbook/trunk/pager) for more information and usage examples. 409 409 410 410 ### Using Raw SQL Queries doc/branches/1.0/book/18-Performance.txt
r4186 r4666 69 69 $articles = ArticlePeer::doSelect($c); 70 70 71 This can be automated by the use of a pager. The `sfPropelPager` object automatically handles the offset and the limit of a Propel query to hydrate only the objects required for a given page. Refer to the API documentationfor more information on this class.71 This can be automated by the use of a pager. The `sfPropelPager` object automatically handles the offset and the limit of a Propel query to hydrate only the objects required for a given page. Refer to the [pager documentation](http://www.symfony-project.com/cookbook/trunk/pager) for more information on this class. 72 72 73 73 ### Minimizing the Number of Queries with Joins