StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3975850
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-10-20T08:06:43.660
FavoriteCount
0
LastActivityDate
2010-10-20T08:06:43.660
LastEditDate
LastEditorUserId
0
OwnerUserId
401019
ParentId
3974358
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I'm going to add to Frankie's answer, because I also believe the OP's current method is going to bite him the butt again one day. The OP may not find this useful, but it could help someone else. You can use <a href="http://site.com/images/20" rel="nofollow">http://site.com/images/20</a>, but the 20 represents an image ID instead of a page number. Of course the query to get the image is simple: <pre><code>SELECT id, img_src FROM pictures WHERE gallery = images AND id = 20 LIMIT 1 </code></pre> As a benefit this query is more efficient than using an offset with the LIMIT clause. But the OP said in a comment that he likes his current system because it doesn't require additional database queries to help build pagination links. Well, that's not a problem here. Lets say you're on the page <a href="http://site.com/images/20" rel="nofollow">http://site.com/images/20</a>. Your page links would be the following: Prev - <a href="http://site.com/images/prev/20" rel="nofollow">http://site.com/images/prev/20</a> Next - <a href="http://site.com/images/next/20" rel="nofollow">http://site.com/images/next/20</a> Obviously it didn't take any additional queries to build those links. They're just a slightly different URL showing the same image ID. But how do they work to move to the next or prev image? Simple. Instead of the above query, you would use one of these: If the prev link was clicked, you use this query: <pre><code>SELECT id, img_src FROM pictures WHERE gallery = 'images' AND id < 20 ORDER BY id DESC LIMIT 1; </code></pre> If the next link was clicked, you use this query: <pre><code>SELECT id, img_src FROM pictures WHERE gallery = 'images' AND id > 20 ORDER BY id ASC LIMIT 1; </code></pre> The first query gives the image that came before the current one, and the second query gives the image that comes after the current one.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPHP and MySQL: Formatting URLs correctly when using pagination to display images of multiple galleries
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmellowsoon
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COThe only thing to remember is to validate the value of $_GET['page']. I'm sure you're aware of this, but if you insert it directly into the SQL query code, visitors could insert their own SQL and do all kinds of ghastly things to your tables.
 singulars
 PostPostId
 PO
 UserUserId
 USWilliam Linton

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.