[dev] Bug #3126

[Duck]

On Saturday 14 January 2006 03:14, Ben Chavet wrote:
> I've been tinkering with it a bit, and am beginning to doubt the
> effectiveness of splitting the root by group_uid.  At least to the
> extent that the current patch does.  For example, agora can have
> multiple group_uid values, so we can't just assume one group_uid per
> app.

We can move control down to API classes. For flattering attributes we need to 
control DT from the ClassObject. To not mess things up we can do the two 
things at the same level and we solve the problem of different group_uid.

> I'm still undecided on whether I like the flattened tables.  Sure,
> they're great for speed, but they limit the flexibility of being able
> to add arbitrary attributes without changing the table structure.

Flattering is an advanced administration feature, that wont be used on an 
average installation, but will allow horde to be used in a larger 
installations. For example if I import my forum data in Agora it results as 
useless. So it should be good documented and leave admin to decide if they 
would like to use it.

Duck