I'm building a modest CMS. In it, i want the ability to "roll" back to previous versions of pages when making updates. I'm unclear as to how i might structure the DB tables to make this efficient. My first thought was to jsut do an insert anytime a page is "updated". However, this creates a new id so i'm not sure how i'll roll back if I don't then have a unique identifier. Also, since every single update would insert a new record, even with proper indexing i'm probably going to create performance issues right? Any suggestions?
"versioning" in a CMS
1 reply to this topic
Posted 28 October 2006 - 04:05 PM
It's not pretty any way you slice it... you just need to have groups of records, where only one is "active", however you decided to deal with this: date ranges, activity fields, etc.
Seriously... if people don't start reading this before posting, I'm going to consider not answering at all.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users