[RESOLVED] How to "Store An Array" for later use

[StevenJ]

I am after an approach to solve a problem I have. I will be able to code it, I just need to know what to code!

Anyway. I Have a MySQL table with a number of records, that will probably not exceed a couple of thousand. Depending on which page the user browses, SQL is run, and it will display a table with a list of records that match the SQL. Up to this point I have no problem.

The table I display contains only parts of the record, and now, What I wish to do, is have links in this table to go to the record and show all details. Again, I can do this.

The part I now need help with is for example.

I query the database, and I get a resposnse and the matching records are 1, 4, 5, 6, 34, 67, 77, 87, 233, 456, 672, 890, 1002 etc.

From the table that displays this, the user clicks on reocrd 456, and all details of record 456 are displayed. for the purpose of this post, I will call this page "displayfullrecord.php"

On the displayfullrecord.php page, I wish to have a previous link to record 233 and a next link to record 672.

What is the best way to acheive this?

I must stress at this point, once the user has navigated to displayfullrecord.php, I then which to enable the user to navigate the records 1, 4, 5, 6, 34, 67, 77, 87, 233, 456, 672, 890, 1002 using only the next and previous links should they wish.

The only way I can think of doing this is to keep executing the SQL that produced the original table, and then selecting the next recocrd from the original match 1, 4, 5, 6, 34, 67, 77, 87, 233, 456, 672, 890, 1002.........

is there a better way of doing this?

to view these records, the user MUST be logged in anyway - so -

would it be sensible to store the original matches 1, 4, 5, 6, 34, 67, 77, 87, 233, 456, 672, 890, 1002 in an array, and make this array a session variable - then I can just navigate using this array? Would that be possible?

If someone can maybe give me any other possible approaches to this - that'd be great.

StevenJ

[Weedpacket]

The session variable would be the method I'd go with, unless there's the possiblity of the database changing while the user is reading, and you want the changes to be made visible as they occur. Then there'd be no choice but to requery the db each time.

[StevenJ]

thanks WP.......I'll probably go with that then. Just wondered if there was another way that I hadn't thought of, or more likely - knew of 🙂

There is the possibility that the db will change, I never thought of that, but even if there was an extra record added, it wouldn't be vital that it was available, and in any case, if the user returned to the starting page - the SQL would be run once more and the record would be available.

A record is unlikely to change, but even if it did - it would only be textual changes in fields, so there would be no "major" consequence of text being incorrect.

In anycase, the only was the record can be upadted is by admin, and in the operating instructions, I can recommend that before any changes are made - that the reocrd is first of all taken off line. I have already included this functionality..........

many thanks

StevenJ

[madwormer2]

I'd just re-query every time.

Being the lazy fool I am 😉