1. 02 Jul, 2002 1 commit
    • Casey Duncan's avatar
      Restored behavior of ZCatalog when arguments with empty string are passed in.... · 091bd091
      Casey Duncan authored
      Restored behavior of ZCatalog when arguments with empty string are passed in. These values are effectively ignored by searchResults. If only empty values are passed, then it returns all results (assuming you passed an empty filter).
      
      Removed "optimize" argument which was an attempt to "fix" searchResults for programmatic use. Also replaced comments this optimized behavior.
      
      Eventually a new API will be added for "explicit" programmatic queries, for now we will suffer along with searchResults as it is. Extending it with additional dwim is not a path worth traveling.
      091bd091
  2. 30 Jun, 2002 5 commits
  3. 29 Jun, 2002 2 commits
  4. 28 Jun, 2002 1 commit
    • Casey Duncan's avatar
      ZCatalog Fixup: · 36404d25
      Casey Duncan authored
        * Collector #446 - Index managment permissions fixed
      
        * Index managment ui is now integrated into ZCatalog rather than being
          a tab leading to the Indexes subobject manage_main
      
      ZCTextIndex fixed to work under this management scheme and now can be instantiated without that silly "extra" record thingy.
      36404d25
  5. 26 Jun, 2002 4 commits
  6. 25 Jun, 2002 3 commits
  7. 24 Jun, 2002 2 commits
  8. 23 Jun, 2002 2 commits
  9. 22 Jun, 2002 5 commits
  10. 21 Jun, 2002 3 commits
    • Andreas Jung's avatar
      7c228e39
    • Chris McDonough's avatar
      *** empty log message *** · 6d246e76
      Chris McDonough authored
      6d246e76
    • Chris McDonough's avatar
      New TransientObjectContainer implementation. · a7d9afc7
      Chris McDonough authored
      Changes:
      
       - More stable under high usage, especially in the face of
         situations under which there are many ZODB conflict
         errors. The previous implementation had stability problems
         when many conflict errors were encountered; especially
         conflicts that were generated as a result of a simultaneous
         change to a subobject of the TOC (such as in the case of a Zope
         application which makes heavy use of both frames and
         sessions).
      
       - More conflict-resistant.  Instead of ignoring the likelihood
         that multiple threads will attempt to perform the same actions
         simultaneously in methods of the TOC (which often causes
         conflicts), the new implementation attempts to avoid conflicts
         by employing a chance-based housekeeping model.  In this model,
         one thread is "elected" by chance to do the kinds of tasks that
         cause the most conflicts.
      
       - Now uses a "timeslice" based model instead of a "ring" based
         model.  This also helps cut down on conflicts and makes
         the code slighly less obfuscated (not much, though! ;-)
      
       - Quite a few more comments in the code.
      
       - Changes to the sessioning stresstest (which exposed the
         bug that made me reimplement the TOC in the first place).
      
       - Updates to unit tests.
      
       - A "HowTransienceWorks.stx" document which attempts to
         explain how the code works.  It's not stellar, but
         it's a start.
      
       - Changes to the TransientObject class that the TOC
         hands out (typically as a "session data object"), in order
         to make invalidation less Rube-Goldberg-ish.
      
      The structure of the TOC object has changed enough that in order to
      maintain b/w compatibility, an in-place upgrade of "old" instances
      is implied by running them with this code.   "Upgraded" instances
      are not backwards-incompatible, however, so folks can hopefully
      move back and forth between Zope versions without much hassle.
      a7d9afc7
  11. 20 Jun, 2002 12 commits