On Thu, Feb 4, 2010 at 9:27 AM, Aryeh Gregor
<Simetrical+wikilist(a)gmail.com> wrote:
1) Our database schema is not set up to handle this
efficiently for
large result sets. At least I don't think so, off the top of my head.
I've never been able to come up with an acceptable data-structure for
flattening on the fly.
(I think acceptable is something like O(1) or O(log something) on
insert, delete, and no worse then something like O(results log
something) on query).
But if you do atomic categories explicitly enumerated on the pages
then you get the right properties, and fast search with intersections
is the same problem as full text search. I.e. solved.
2) In practice, collapsing categories like this can
often lead to
crazy stuff being included, because subcategory relations aren't used
strictly in a "everything in category A is also in category B" sense.
Yea, automatic collapsing is mostly good for hilarious results...
manual collapsing OTOH.