Home/ Questions/Q 6324409
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T16:41:52+00:00

At the moment I’ve got a big Entity Data Model (.edmx) with a database

  • 0

At the moment I’ve got a big Entity Data Model (.edmx) with a database underneath it. Now I want to give people who use my site the option to edit those entities but only after I gave approval of the change.

So this would mean that I want to “change” the entity but not really save it yet, after I accepted the change it would override the enity with the changed one. But when I did this I would still like to be able to rollback the change afterwards.

Now I’ve come up with a few solutions:

1) Make a entity with like: [ID], [ChangeApplyDate] [ChangeApproveDate] [Entity before change] [Entity after change] [Accepted (boolean)]

2) Make an extra entity with the changed values and a link to the “Original” entity and have a boolean in this entity if it is the current approved one or not. (this would not create a new table but expand the table like, “Book”, with a few extra properties.

Now I would like to know how you think about those solutions and if you ever made something like this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are two things here:

    1. Keep a list of all previous versions. Have a look at my answer to this question: Ideas on database design for capturing audit trails

    2. Controll the acceptance of changes. To do this you could add an approval flag to each table, which only you have access to.

    • 0