>> >> Suppose A buys B manufactured by C. When A or C go out of scope (die, >> e.g.), it doesn't mean the end of B, right? > > It all depends on what the resource is. Often with /A/B/C, C is a > logical subcategory of B, and B of A. So if B ceases to exist, all C's > disappear too. >
Hmm. Consider Toyota has manufactured a dozen of certain cars. I _hardly_ imagine if Toyota drops (ever:) those dozen of cars will _immediately_ disappear too. Personally, I think cascade-on-deletion is just a convenient way to simplify sql queries which otherwise should constantly be aware of possible NULL dereferences. So cascade-on-deletion is totally due to sql misfeature in this area. In contrary, cascade-on-update has applied sense, since no object ceases due to this operation. -- Vladimir -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
