Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8779147
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T19:42:43+00:00 2026-06-13T19:42:43+00:00

I would like to know what is the best way to create next/previous buttons

  • 0

I would like to know what is the best way to create next/previous buttons for an entry in the database.
Let’s say we have a table with images and every image has an ID and a Path.
If the current image has ID equal to “9” how can I get the next and the previous IDs?

I already found a solution for this right here
https://stackoverflow.com/a/8874382
but this seems to be the latest choice. If we have over 10000 entries (images) in our database, this will overwhelm the server. First of all, it selects all entries and then it tries to copy all of the results in an array. After this, the array is searched for the current ID. It’s very slow.

I was thinking about a limit set to the query but how can I get the next and previous pictures after this?

Another (better, I think) solution would be to get the ID of the current picture and decrement/increment it until another image with the new ID is found. I think this is faster than the function provided in the link.

Also, in the same link there is another idea, to set the prev_id and next_id in the model of the current picture. But here we have the same problem, how do we find them? And even if we find them, is it correct to store data about prev/next pictures in the current picture? It does not seem to be right but I’m sure it’s more convenient when you need to access that data.

Thank you!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-13T19:42:45+00:00Added an answer on June 13, 2026 at 7:42 pm

    This query will only returns the next/previous row, if found. Better?
    (Should be implemented in your model class).

    public function getNextId()
    {
        $record=self::model()->find(array(
                'condition' => 'id>:current_id',
                'order' => 'id ASC',
                'limit' => 1,
                'params'=>array(':current_id'=>$this->id),
        ));
        if($record!==null)
            return $record->id;
        return null;
    }
    public function getPreviousId()
    {
        $record=self::model()->find(array(
                'condition' => 'id<:current_id',
                'order' => 'id DESC',
                'limit' => 1,
                'params'=>array(':current_id'=>$this->id),
        ));
        if($record!==null)
            return $record->id;
        return null;
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I would like to know from others' experience the best way to create sitemaps
I would like to know the best way to create a simple html file
I would like to know what's the best way to organize my php project
I would like to know What is the best way to include 3rd party
I would like to know how to use Queue in the best functional way.
I would like to know what is the best, fastest and easiest way to
I would like to know what the best way (performance wise) to access a
I would like to know what is the best way of creating a report
I'm designing a DB and would like to know the best way to store
I'm creating a WPF app and I would like to know the best way

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.