Re: gallery ordering issue

Quoting Ben Chavet <[email protected]>:

> I did it this way for performance reasons.  It would definitely be 
> easier to do a parent-child relationship, but getting a list of 
> galleries that way takes a huge performance hit.  This is especially 
> true when you start to get a lot of images.

Ah, yes, I remember this conversation now. I don't need this to happen, 
but one
thing you could do is build a

> I'd still like to see better performance, and I have also considered 
> the option of breaking ansel away from the horde_datatree table.  
> Even if it were to use something like ansel_datatree and 
> ansel_datatree_attributes.

There's been a TODO in horde/docs/TODO to make this generically possible for
quite a while now. It's a good idea. I'd prefer not to go to a completely
custom driver, though.

> It was not nearly as robust or as flexible as ansel, which is why I 
> abandoned it, but it was much more responsive when getting the 
> gallery lists and photos in the galleries.

Not saying that we can't or shouldn't get better, but there are always 
going to
be tradeoffs there. :)

> I'm not looking to change ansel's structure, especially as we are 
> getting close to a horde release.  Maybe the performance I am looking 
> for is hiding in the datatree classes somewhere.

Allowing breaking things out into seperate tables would help a *lot* - 
you'd cut
group_uid out of the WHERE clauses of all of the queries, and that'd help with
query optimization a bunch. There are probably other queries that can be
optimized, and indexes that can be added. Help finding those would be *very*
welcome.

-chuck

--
"Regard my poor demoralized mule!" - Juan Valdez
-- 
ansel mailing list - Join the hunt: http://horde.org/bounties/#ansel
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]