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
On Mon, Jul 28, 2008 at 11:58 AM, Nate Tallman
<[EMAIL PROTECTED]> wrote:
> Hey guys,
> Does anyone know of any good literature on programming revision history into
> an application? I'm looking for something covering theory around revision
> history.
>
> For a little background info, I'm dealing w
2 matches
Mail list logo
