StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1829468
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-12-01T22:44:47.400
FavoriteCount
0
LastActivityDate
2011-03-23T17:07:27.050
LastEditDate
2011-03-23T17:07:27.050
LastEditorUserId
138475
OwnerUserId
138475
ParentId
1829381
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
About this problem, you might be interested by this section of the manual : <a href="http://framework.zend.com/manual/en/zend.paginator.usage.html#zend.paginator.usage.dbselect" rel="nofollow noreferrer">39.2.2. The DbSelect and DbTableSelect adapter</a>, which states (quoting, emphasis mine) : <blockquote> ... the database adapters require a more detailed explanation. Contrary to popular believe, these adapters do not fetch all records from the database in order to count them. Instead, the adapters manipulates the original query to produce the corresponding <code>COUNT</code> query. Paginator then executes that <code>COUNT</code> query to get the number of rows. This does require an extra round-trip to the database, but this is many times faster than fetching an entire result set and using <code>count()</code>. Especially with large collections of data. </blockquote> (There is more to read on that page -- and there is an example that should give you more information) The idea is that you will not fetch all data yourself anymore, but you'll tell to <code>Zend_Paginator</code> which Adapter it must use to access your data. This Adapter will be specific to "Data that is fetched via an SQL query", and will know how to paginate it directly on the database side -- which means fetching only what is required, and not all data like you initialy did.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POZend_Paginator; is it optimized?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USPascal MARTIN
UserOwnerUserId
1. USPascal MARTIN
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POZend_Paginator; is it optimized?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.