Temp table or not

[programmer79]

I am creating an area where an administrator will add a vehicle to the database. the first page will accept the info such as make, model, features, etc and the second page will be the area where the admin will upload the picture(s) for the vehicle. I am debating if I should have a temp table to store the information from the two pages and then dump it into the live db once everything is complete, or if I should store the info in variables, sessions, etc. An example would be adding a new item on ebay where you do this over multiple pages. Any thoughts would be appreciated.

Thank you,

tony

[nemonoman]

I think it's a matter of opinion, but be aware that you really need to consider behaviors as users jump back and forth between form pages. Browser behavior when clicking the back button is unpredictable.

I'd put everything on one page, for starters.

I LOVE temporary records!

I store temporary values such as those you describe in a table. When the perm record is saved, I delete the record.

I also store the ID of the record in a cookie.

Next time the user clicks into the site, I check to see if that cookie exists. If it does, it means user exited before doing a permanent save. SO, If it does, I delete the record.

[greg252]

I would put it all on 1 page. Then there is no need for a temp table.