Hi Taesung,

This is not related to the Store source code nor to an sproc! This is related to a rule maintaining database integrity. You can't delete a cetegory if this one contains one or several categories or if the category is linked to one or several products. Allowing to delete a non empty category is definitively too risky! Imagine if you delete "by error" a category containing several sub categories and thousands products related.

To override this safety database design, you have two choices:

1. The first is to create an sproc to:
   1. parse the sub categories of the category to deleted
   2. if the current category do not have parent then:
      1. update products from the current category to a replacement category
      2. or delete them, in this case what are you doing with the orders using those products?
   3. else:
      1. call your sproc (recurse) with the current categoryID and the replacement categoryID
2. The second is to delete or replace the following database constraints:
   1. FK_dnn_Store_Categories_dnn_Store_Categories
   2. FK_dnn_Store_Products_dnn_Store_Categories
      dnn_ is my object qualifier in my dnn db instance

My choice is to not allow this kind of dangerous "feature".

Gilles

---

We (team members) are Humans offering their knowledge, their work and their spare time FOR FREE to benefit the community. It would be so particularly appreciated that your messages begin with "Hello" and end with "Thank you" or any other form of politeness. Ask yourself what your reaction would be, if you were approached by me (a total stranger) on the street to ask you something without saying "Hello" nor "Thank you"? After several years of services dedicated to the community, I begin to be tired to read requests without any form of politeness.