1. 24 Jul, 2018 13 commits
  2. 19 Jul, 2018 1 commit
  3. 17 Jul, 2018 3 commits
  4. 13 Jul, 2018 1 commit
  5. 12 Jul, 2018 2 commits
  6. 11 Jul, 2018 2 commits
  7. 09 Jul, 2018 1 commit
  8. 06 Jul, 2018 1 commit
  9. 05 Jul, 2018 13 commits
  10. 04 Jul, 2018 3 commits
    • Vincent Pelletier's avatar
      CMFActivity: Get rid of an outdated comment. · bc65ba72
      Vincent Pelletier authored
      The original need to touch this comment is that it mentions now-removed
      Folder_reindexObjectList script. But also:
      - it mentions multi-ZEO setups, which are now discouraged if favour of
        using NEO
      - it mentions pre-conceived optimisations, which can be wrong and hence
        misleading (up-to-date measures are needed before deciding what to
        optimise)
      - it mentions a number of activity nodes which is nowadays exceeded
        without seeing any obvious issue caused by activity table deadlocks
        (which are nevertheless still likely an issue, just not yet breaking
        scalability)
      bc65ba72
    • Vincent Pelletier's avatar
      all: Get rid of Folder_reindex{All,Objectlist,TreeObjectList} · e944e1ef
      Vincent Pelletier authored
      These are now superseded by recursiveReindexObject.
      e944e1ef
    • Vincent Pelletier's avatar
      all: Remove recursiveImmediateReindexObject, and references to it. · c0b284be
      Vincent Pelletier authored
      This method does not belong to Folder (nor Base, even as an alias), as
      it recurses wihout any limit in a tree whose node count is unknown.
      Such generic recursion should either be deferred (split in multiple
      transactions, each processing a limited chunk of the tree) or not be
      recursive (which of course depends on the need).
      There is a single caller left (constructInstance) where the subtree size
      is assumed to be reasonable, as it was constructed inside current
      transaction. So essentially rename this method so it is only used in such
      conditions.
      c0b284be