Re: Programming With Revision History

Hello, Think in this way: You would be needing two tables: first one: content table: contentID, contentType, revisionID ----------- contentID is the PK ( you can make the UI for adding and deleting these fields) content_revisions table revisionID, contentID, ---------- revisionID is the PK Great things start from simple thinking. You can use this model to implement revisions. In some PHP CMS we currently have they also use serialized data fields for each revision. --- Thanks