1. 17 Jan, 2017 1 commit
  2. 13 Jan, 2017 1 commit
  3. 12 Jan, 2017 1 commit
  4. 11 Jan, 2017 3 commits
  5. 10 Jan, 2017 1 commit
  6. 09 Jan, 2017 22 commits
  7. 08 Jan, 2017 1 commit
  8. 06 Jan, 2017 4 commits
    • Boris Kocherov's avatar
      f26f409c
    • Vincent Pelletier's avatar
    • Vincent Pelletier's avatar
      CMFCategory: Do not index any Base Category as a related document. · 95e3eaec
      Vincent Pelletier authored
      Without this change, "source/a/b" in non-strict mode indexes:
        (document.uid, source.uid, b.uid, 1)
        (document.uid, source.uid, a.uid, 0)
        (document.uid, source.uid, source.uid, 0)
      This last line does not contain anything which cannot be found by looking
      at the base category uid column, so it is wasting disk (and index) space,
      costing performance.
      But keep indexing a Base Category document if is it not the base category
      for considered relation. It is not clear whether stopping indexation at the
      first encountered Base Category document is intentional, or if recursion
      should only stop when reaching the base category of considered relation.
      With this change, "source/a/b" in non-strict mode indexes:
        (document.uid, source.uid, b.uid, 1)
        (document.uid, source.uid, a.uid, 0)
      removing the redundancy.
      95e3eaec
    • Vincent Pelletier's avatar
      CMFCategory.CategoryTool: Stop using selection_{report,domain} · 2b20a1d8
      Vincent Pelletier authored
      It is overkill, and is likely slower than just passing the needed
      values straight to catalog.
      Also, rely on duck-typing instad of portal-type-testing.
      Also, drop unused "spec" and "filter" arguments.
      Also, expose strict{,_membership} used arguments, simplifying code.
      Keep catchall **kw for compatibility.
      2b20a1d8
  9. 05 Jan, 2017 1 commit
  10. 04 Jan, 2017 1 commit
  11. 03 Jan, 2017 4 commits