> My current thought is to use a temp table(s) that: > a. when visiting an "edit" page - LOADS the live data into the temp table > b. all editing is done in the temp table > c. once he likes it, he can hit the "publish" button, and the temp data > replaces whatever is currently in the live table. > d. after that transaction is completed, the temp table is emptied again > > Seem like a plan? Is there a better way? How does everybody else handle > this stuff?
I would create an actual persistent table for this - if you literally mean a temporary table, that table will only last while the database session is active, and could go out of scope before the user has completed his edits. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:350504 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
