[Tickets #7347] Hierarchical SQL share driver needs to correctly deal with children when deleting a share

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7347
------------------------------------------------------------------------------
  Ticket             | 7347
  Created By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Hierarchical SQL share driver needs to correctly deal
                     | with children when deleting a share
  Queue              | Horde Framework Packages
  Version            | HEAD
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          | Horde 3.3
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2008-09-16 20:06) wrote:

This is more of a 'potential' bug since no client code is affected by  
this yet, but currently nothing is done about a share's children when  
deleting a share. i.e. It's orphaned in the database. We need to  
delete all children of a share when deleting the share. It will be up  
to the client code to determine if it is OK to delete a share with  
children.

Since it's *possible* that a child share could be owned by a different  
user (and not even visible to the parent's owner), we need to decide  
how to handle deletion. After discussing this with Chuck, I'm thinking  
we say that if a user is able to delete a share, he/she will also be  
able to delete any children. Similar to directory permissions on a  
unix system. Any agreement/disagreements?

This really should be done for Horde 3.3