Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • But doesn't it affect the application's performance to check the item before it's displayed "every time" whether it's deleted or not! and also to manage the hierarchical structure that I have, it won't stop at just a single column, I'll have to add to the objects that are less in the hierarchy an extra column to check if it's parent is deleted so It should also be deleted! .. could you let me what do you think about my second approach :) ? and thanks a lot for your time! Commented Mar 9, 2011 at 3:54
  • Ya it will affect some performance, but you can manage the performance depending upon your application strength. But i think if you will add the record in other table to make the entry delete then it will create more overhead then this. Commented Mar 9, 2011 at 3:58
  • I'm sorry, I don't understand how come having a separate table will be an overhead! .. I'll delete an item, it's all moved to another table and I don't have to check the items when I display them! .. I'll pay the cost in performance when moving a lot of stuff but this will performance will appear to me (the administrator) and it's okay for the owner to face some delays, in order to let my visitors have a better experience (a faster application) .. Am I missing something or thinking the wrong way ? Commented Mar 9, 2011 at 4:03