| Summary | Hierarchical SQL share driver needs to correctly deal with children when deleting a share |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | mrubinsk (at) horde (dot) org |
| Created | 09/17/2008 (6135 days ago) |
| Due | |
| Updated | 09/19/2008 (6133 days ago) |
| Assigned | |
| Resolved | 09/19/2008 (6133 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | 3.3 |
| Patch | No |
http://cvs.horde.org/diff.php/framework/Share/Share/sql_hierarchical.php?r1=1.17.2.22&r2=1.17.2.23&ty=u
http://cvs.horde.org/diff.php/framework/Share/Share/sql_hierarchical.php?r1=1.44&r2=1.45&ty=u
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒ Horde 3.3
Assigned to Michael Rubinsky
Queue ⇒ Horde Framework Packages
Summary ⇒ Hierarchical SQL share driver needs to correctly deal with children when deleting a share
Type ⇒ Bug
State ⇒ Assigned
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