6.0.0-beta1
9/24/25

[#3280] Share information access within DataTree is too slow
Summary Share information access within DataTree is too slow
Queue Horde Framework Packages
Queue Version FRAMEWORK_3
Type Bug
State Not A Bug
Priority 3. High
Owners
Requester leena.heino (at) uta (dot) fi
Created 01/17/2006 (7190 days ago)
Due
Updated 01/17/2006 (7190 days ago)
Assigned
Resolved 01/17/2006 (7190 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
01/17/2006 10:42:57 AM leena (dot) heino (at) uta (dot) fi Comment #3 Reply to this comment
No, because the share system is a wrapper around the permissions
system which is too flexible to be translatable into a flat table.
This unfortunately means that for any larger organization the x.1 H3 
versions of turba, nag, mnemo and kronolith are absolutely useless as 
long as the permission system is tied to the current implementation of 
DataTree. DataTree access as it is now is way too slow for it's 
intended task.
01/17/2006 09:54:47 AM Jan Schneider Comment #2
State ⇒ Not A Bug
Reply to this comment
Would it be possible to remove share information from DataTree and
change it to use flat database table. Change similar to the way
history information was removed from DataTree.
No, because the share system is a wrapper around the permissions 
system which is too flexible to be translatable into a flat table.
01/17/2006 08:38:07 AM leena (dot) heino (at) uta (dot) fi Comment #1
State ⇒ Unconfirmed
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Share information access within DataTree is too slow
Queue ⇒ Horde Framework Packages
Reply to this comment
We tried to use the H3 x.1 rc versions of the horde, imp, turba, 
kronolith, nag, mnemo. It seems that DataTree performace is once again 
an update blocker. This time it is the way the share information is 
saved, read and accessed from DataTree.



It seems that share information is used and accessed more often 
compared to H3 x.0 versions. This means that DataTree is accessed more 
often and this results to sql queries that take far to long to 
complete. Single share related query from DataTree can take tens of 
seconds to complete.



Would it be possible to remove share information from DataTree and 
change it to use flat database table. Change similar to the way 
history information was removed from DataTree.

Saved Queries