StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2857364
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-05-18T12:52:03.890
FavoriteCount
0
LastActivityDate
2012-02-12T03:28:05.453
LastEditDate
2012-02-12T03:28:05.453
LastEditorUserId
315562
OwnerUserId
315562
ParentId
2489422
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Firstly, you should be looking at the <a href="http://developer.yahoo.com/yql/guide/yql-opentables-reference.html#yql-opentables-paging" rel="nofollow noreferrer">paging model</a> (Your link got compressed above, so I'm just putting it here. When you use the paging with no <code><execute></execute></code> block specified, it will be used in the query string with the URL specified in <code><url></url></code>. Just play with the <a href="http://developer.yahoo.com/yql/guide/yql-opentables-sample.html#yql-opentables-sample-flickr-photo-search" rel="nofollow noreferrer">Flickr Photo Search Example</a>, you have to run it in the Console with Diagnostics turned on to look at the changes in the URL. The <code>id</code> attribute is used to insert the number in the query. Just to illustrate here, the paging portion looks like this: <pre><code> <paging model="page"> <start id="page" default="0" /> <pagesize id="per_page" max="250" /> <total default="10" /> </paging> </code></pre> For example, querying <pre><code>select * from flickr.photos.search(10,20) where has_geo="true"` </code></pre> The URL used was <code>http://api.flickr.com/services/rest/?method=flickr.photos.search&has_geo=true&page=1&per_page=30</code>. As you can see, it actually took the <code>page=1</code> but asked for <code>per_page=30</code> and internally truncated the first 10 results so that you get an offset of 10 and a total of 20 results. The reason why YQL did this is because the model selected is <code>page</code>. Another example, if you attempt to do this: <pre><code>select * from flickr.photos.search(249,2) where has_geo="true" </code></pre> YQL will retrieve both <code>...&page=1&per_page=250</code> and <code>...&page=2&per_page=250</code> (I've shortened the urls for illustration) as expected to get the results. The paging variables are also defined in the global scope if you use JavaScript in <code><execute></execute></code> section. You can see this being used in the <a href="http://github.com/yql/yql-tables/blob/master/flickr/flickr.photos.astro.xml" rel="nofollow noreferrer">flickr.photos.astro OpenData Table</a>. I guess that should answer the question for you, since I see that <a href="http://github.com/yql/yql-tables/blob/master/mozillalabs/jetpackgallery/mozillalabs.jetpackgallery.tag.info.xml" rel="nofollow noreferrer">on GitHub</a>, you have been working on how to extract the pages using XPath. For your case you should have something like: <pre><code> <paging model="page"> <start id="page" default="1" /> <pagesize id="per_page" max="10" /> <total default="10" /> </paging> </code></pre> The <code>per_page</code> would be in your internal query but it's used for the YQL to determine the queries needed. Then in your JavaScript could probably do something like: <pre><code> y.query( "select * from html where url=@url", {url: "http://jetpackgallery.mozillalabs.com/jetpacks?page=" + page} ); </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to implement YQL paging?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USsirhc
UserOwnerUserId
1. USsirhc
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to implement YQL paging?
 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
 VTBountyClose
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.