Or have a 'versions' table attached to the 'page' table. Versions can have status, with a maximum of 1 'published' for any given pageID, and versions can have publicationStart and publicationEnd dates. Gives you the flexibility of rolling back to previous versions as well. Just a thought.
---------------------------------------- From: "Les Mizzell" <lesm...@bellsouth.net> Sent: Wednesday, March 21, 2012 12:22 PM To: "cf-talk" <cf-talk@houseoffusion.com> Subject: Admin System - Temp Tables? Advice? I'm in the process of rewriting the admin system for an older website. On this version, client want to be able to edit/add/delete anything at will, and have it NOT got live until he's decided he's "done" with that part. 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? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:350502 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
