how can I simulate the trash concept in my webApp?

Question

I'm actually working on a webApp, and i want to simulate the TRASH concept, so each element deleted from the application will disappear, but remain for the administrator in the trash area so he can confirm its deletion.

I've suggested to add an attribute IsArchived with the Boolean type, so it can indicate if the element is deleted or not, but it appears that this method is old fashioned, and I think that it will deteriorate the performances of the app ... so is there any paradigm or method I can use to simulate this principle and optimizing the performance of the app ?

PS : I'm Using MYSQL as a database.

http://stackoverflow.com/q/2549839/1700321. – Aleksandr M Jul 18 '14 at 11:35 — Aleksandr M, Jul 18 '14 at 11:35

Petr Mensik · Accepted Answer · 2014-07-18T13:02:13.747

2

I don't think there is something wrong with having deleted attribute in the table of your elements, seems to me like the easiest and most efficient way. You could also create a duplicate table of your elements and move the deleted ones here, this really depends on the case. But I would gor for number one, recycle bin seems to me as a good use case of soft-deleting because otherwise you would be moving rows from one table to another all the time.

edited Jul 18 '14 at 13:02

answered Jul 18 '14 at 11:32

Petr Mensik

26,874
17
90
115

does the " WHERE IsArchived=0 " doesn't affect the performances of the queries ? – TheByeByeMan Jul 18 '14 at 11:49
2

Of course it does - but in a way that I really doubt you would notice the difference. – Petr Mensik Jul 18 '14 at 11:58

how can I simulate the trash concept in my webApp?

1 Answers1