Question about pagination

Beatnik

I have a couple of pages that display only a single record from a particular table and some other various information related to that particular record from other tables.

I would like to be able to "scroll" through the record with previous / next buttons I have set up. So far everything I have found about pagination leads me to believe that pagination is geared more twords viewing multiple 'pages' of many records per page.

Is there another or better way to handle single record pages or should I look more into setting up a pagination with a limit of 1 per page?

Thanks much for any info / advice you may be able to provide.

dagon

pagination is breaking any set of material in to pages. Your right in that its more common in viewing multiple records per page. But theres no reason you cant do what you want. However by my reading sounds like you could jsut add links to 'sections' for that particular record.

Say it was a person, First page may have basic details then a link to address, a link to a picture, a link to ??

saying page 1,2,3 is not very informative when those pages contain quantifiable information you can label.

Beatnik

I have been reading about pagination and it seems like it could do what I am looking for, I just wasnt sure if there might be a better / easier way.

Basically the page is information about a particular job, at the top is the job information. Under that is a short form to add items this particular job requires. At the bottom is the list of added items.

After adding the items need for a particular job_id I would like to be able to simply click to the next job.

Hope this makes sense.

Thanks for the reply, I will continue looking into pagination as I will want to learn it eventually regardless but if there is a better / easier way I would like to know that as well.

dagon

I wouldn't call that pagination.

When you get job 1 you also select the id for job 2 and put that in the "next" link

alternativly sending job 1's id i the "next" link in enables getting job 2

depends on db etc.