Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[osee-dev] RE: The Concept of Undelete

It seems that replace with version is a more general solution, so that is an advantage. Would the replace with version idea use the previous modification type or something else?  Also how would it apply to the case where an artifact with children had been deleted?

Thanks,
Ryan Brooks

-----Original Message-----
From: osee-dev-bounces@xxxxxxxxxxx [mailto:osee-dev-bounces@xxxxxxxxxxx] On Behalf Of Phillips, Jeff C
Sent: Monday, October 26, 2009 11:12 AM
To: OSEE Developers mailing list
Subject: [osee-dev] RE: The Concept of Undelete

Something that could support the idea of undelete and more...

There has been an idea to replace the current revert logic which removes data from the database with a transaction based idea of replace with version. The concept of revert was to allow users the ability to safely undo changes made to branches.

The approach of replace with version would allow users to be able to perform an undelete action as well as allow them to be able to do a replace as head concept. Users would be able to bring objects back from deletion and even be able to make a previous version the current version with a transaction history of the changes.

Thanks,
Jeff Phillips
 

-----Original Message-----
From: osee-dev-bounces@xxxxxxxxxxx [mailto:osee-dev-bounces@xxxxxxxxxxx] On Behalf Of Brooks, Ryan D
Sent: Monday, October 26, 2009 10:44 AM
To: OSEE Developers mailing list
Subject: [osee-dev] The Concept of Undelete

Developers,

A number of use cases have been identified that appear to involve the concept of undelete.  These cases are:
   1.  a user deleted an artifact and then wishes to undo the deletion:  currently handled using revert which is less than ideal since it leaves no history of its occurrence
   2.  same as case 1 but for a relation - this case has the additional implication of needing to preserve the relation identity to aid in conflict detection
   3.  same as case 1 but for an attribute

A related case that does not involve deletion is when a user wishes to go back to a previous version of an attribute.

This brings up the question of what modification type(s) would be used in the osee_txs table for such cases.  Also how will this be conceptually presented to the users.

Thanks,
Ryan Brooks


_______________________________________________
osee-dev mailing list
osee-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/osee-dev
_______________________________________________
osee-dev mailing list
osee-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/osee-dev


Back to the top