I can't figure out how to pull the target record, plus the one before and after it in a single SQL query. I suppose that can't be done.

It can be done, though it's not particularly efficient, and the exact syntax of the query will depend on which database you're using. The strategy is to outer join the table to itself twice (once for the prev, once for the next). Something like (in Oracle):

 select max(P.img_id), T.img_id, min(N.img_id)
 from images T, images P, images N
 where P.img_id(+) < T.img_id and P.uid(+) = T.uid and P.album_id(+) =
+ T.album_id
   and N.img_id(+) > T.img_id and N.uid(+) = T.uid and N.album_id(+) =
+ T.album_id
   and T.img_id = ? and T.uid = ? and T.album_id = ?
 group by T.img_id
[download]

That said, grabbing the array is a better way to do it.
Update: added other outer-joined columns.

---

We're not really tightening our belts, it just feels that way because we're getting fatter.

---

In reply to Re: Building an index for next/last in a photo album. by Roy Johnson
in thread Building an index for next/last in a photo album. by Seumas

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

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.