Data versioning design issues?

is making a system. The logic is probably this:

New forms can be saved later or submitted to an administrator for review. The audit does not pass the person who will call back to fill in the form.
Every step in this will produce a version, and different versions of the operation will have to differ.
For example, the save operation will produce a saved version, the submission will produce a committed version, the Administrator audit does not pass the call back to the form will also produce a corresponding type of version number. People of different roles see the list of versions differently.
Later, you'll compare these stored versions with the results of Word review, and see the differences between versions.

The current practice is to add a version field to the table. Adds a record for each version produced. The tracking change function is to generate two static pages for comparison.
But the total sense of this is too dead, and the page will produce a large problem of efficiency.

Here to ask you the great God, what is the design of this kind of plan?

Reply content:

is making a system. The logic is probably this:

New forms can be saved later or submitted to an administrator for review. The audit does not pass the person who will call back to fill in the form.
Every step in this will produce a version, and different versions of the operation will have to differ.
For example, the save operation will produce a saved version, the submission will produce a committed version, the Administrator audit does not pass the call back to the form will also produce a corresponding type of version number. People of different roles see the list of versions differently.
Later, you'll compare these stored versions with the results of Word review, and see the differences between versions.

The current practice is to add a version field to the table. Adds a record for each version produced. The tracking change function is to generate two static pages for comparison.
But the total sense of this is too dead, and the page will produce a large problem of efficiency.

Here to ask you the great God, what is the design of this kind of plan?

This requirement, like SVN or git, is a bit similar and can be consulted

