Despite what has been said in another reply - NEVER RELY ON THE ORDER IN WHICH DATA IS RETURNED. In MySQL it is possible that ANY change of the data in a table will change the order of items being returned

I would have an indentity field in each record which could be an auto-incremented value (one counter for all users) then when you select the records for a single user you can retrieve them ordered by ID. Then do one of two things, either embed the ID for the next and previous. Or you can do a query which asks for ID > lastID for the next record or ID < lastID for the previous.

This way, the user could add a new image while somebody is scanning through them and the new one would be found at the end.

Their are a number of more sophisticated ways to handle this. I wrote a gallery for internal use here a couple of years ago. The user uploads the images in any order they like, then Using a simple interface they can create the sequence they wish the images to appear in. This creates a hash which is stored in their user record which maps sequence number to ID. They can edit the list to insert a new image into the sequence or remove one.

Good luck! jdtoronto

In reply to Re: next prev record mysql table by jdtoronto
in thread next prev record mysql table by jwlarson3rd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.