Summary | VFS musql driver rewrite |
Queue | Horde Framework Packages |
Queue Version | HEAD |
Type | Enhancement |
State | Assigned |
Priority | 1. Low |
Owners | bklang (at) horde (dot) org |
Requester | bklang (at) horde (dot) org |
Created | 12/29/2006 (6711 days ago) |
Due | |
Updated | 12/13/2010 (5266 days ago) |
Assigned | 11/08/2008 (6031 days ago) |
Resolved | |
Milestone | Horde 4.0 |
Patch | Yes |
State ⇒ Assigned
State ⇒ Stalled
think it is better to put this off until H4 and a hopefully improved
VFS API. I'll stall this for now.
Horde 4.0 milestone and stall the ticket for now while we work on the
Horde 3.2 releases?
updated version.
Assigned to Ben Klang
State ⇒ Assigned
libraries. I'm not sure if it'd be possible to delegate permissions
and group checking to a separate object, which could be supplied by
Horde?
State ⇒ Feedback
ticket #4819, the VFS library must not useany Horde internals. It's a completely standalone package distributed
through PEAR.
New Attachment: muvfs-sql-index-and-group.patch
as enforce path/name uniqueness at the DB level.
Priority ⇒ 1. Low
State ⇒ New
New Attachment: musql-rewrite.patch
Queue ⇒ Horde Framework Packages
Summary ⇒ VFS musql driver rewrite
Type ⇒ Enhancement
and I will post it.
This is nearly a complete rewrite of the musql VFS driver. All
permissions setting and enforcing are now working. Checking is done
both for the user and group, as well as "other." This should be
backward compatible to the SQL driver from a DB perspective. That is
to say that I have used the old SQL driver with the MUSQL table and it
worked without errors. Of course the MUSQL driver does require the
updated DB schema to function.
I have attempted to test it thoroughly and at this point there are no
more known bugs. The only potentially confusing item may be that the
permissions for the root directory come from Perms:: rather than VFS.
This is because there is no way to set the perms on the root folder
directly.