1. 24 Oct, 2018 1 commit
  2. 14 Oct, 2018 2 commits
  3. 03 Oct, 2018 1 commit
  4. 21 Sep, 2018 1 commit
  5. 31 Aug, 2018 1 commit
  6. 22 Aug, 2018 7 commits
  7. 16 May, 2018 1 commit
  8. 09 May, 2018 1 commit
  9. 02 Apr, 2018 1 commit
  10. 27 Mar, 2018 1 commit
  11. 26 Mar, 2018 3 commits
  12. 25 Mar, 2018 1 commit
  13. 10 Mar, 2018 1 commit
  14. 09 Mar, 2018 1 commit
  15. 15 Feb, 2018 1 commit
    • Jim Fulton's avatar
      Avoid seeking on import (#188) · 2115c90a
      Jim Fulton authored
      * Don't seek on imports
      
      (other than the possible seek for custom importers)
      
      We were seeking to handle blob markers. This has two major drawbacks:
      
      1. It wasn't possible to use a non-seekable file.  A use case for
         export/import is to copy database data.  An intermediate file, and
         associated I/O, could be avoided using a pipe, but pipes aren't
         seekable.
      
      2. Seeks cause file-buffer data to be discarded, making IO far more
         expensive.
      
      We didn't really need blob markers, because the preceeding blob data
      records serve as markers.  (Now we're stuck with them for backward
      compatibility.)
      
      * Make cp's buffer size larger and configurable.
      
      * Use the storage temprary directory when importing blobs
      
      To avoid an extra copy.
      
      Also, allow the copy (cp) buffer sie to be overridden on export.
      
      (I see no obvious way to plumb it on import. :( )
      
      * Oops, need to use a binary literal (Python 3)
      
      * Respond to PR comments
      2115c90a
  16. 14 Nov, 2017 1 commit
    • Jim Fulton's avatar
      Update the front page to be a little less negative. (#186) · de1f24ca
      Jim Fulton authored
      Especially with regard to write capacity and search.
      
      This hasn't been updated in a while and I feel that it is out of date.
      
      I feel that this could use more work, but I'm anxious to do an
      incremental improvement given the screencast I just released. :)
      de1f24ca
  17. 13 Nov, 2017 2 commits
  18. 12 Nov, 2017 1 commit
  19. 08 Nov, 2017 1 commit
    • Julien Muchembled's avatar
      Review Connection/DB closure · 1b9475d4
      Julien Muchembled authored
      In addition to some micro-optimisation, this fixes the following minor issues:
      - Closing a DB left Connections registered to the global transaction manager.
        Which broke at least multi-db because only such primary connections were
        ignored with monkey-patches.
      - Stop calling the real newTransaction when aborting an existing transaction.
        This was not the case if explicit_transactions=0.
      1b9475d4
  20. 07 Nov, 2017 1 commit
  21. 30 Oct, 2017 1 commit
  22. 27 Oct, 2017 2 commits
  23. 05 Oct, 2017 1 commit
  24. 30 Aug, 2017 2 commits
  25. 29 Aug, 2017 2 commits
    • Jason Madden's avatar
      Use a higher pickle protocol for serializing objects on Python 2 (#179) · be5a9d54
      Jason Madden authored
      * Use a higher pickle protocol (2) for serializing objects on Python 2
      
      Previously protocol 1 was used. This is more efficient for new-style
      classes (all persistent objects are new-style), according to the docs,
      at the cost of being very slightly less space efficient for old-style
      classes.
      
      In tests of a persistent object with two trivial numeric attributes,
      the higher protocol was 12 bytes smaller, and serialized and
      deserialized 1us faster. Introducing a reference to another new-style
      class for a more realistic test made the higher protocol twice as fast
      to serialize (20.5 vs 10.3us), almost half the size (215 vs 142
      bytes), and it deserialized 30% faster (6.5 vs 4.6us).
      
      On Python 2, this will now allow open ``file`` objects to be
      pickled (loading the object will result in a closed file); previously
      this would result in a ``TypeError`` (as does under Python 3). We had
      tests that you couldn't do that with a BlobFile so I had to update it
      to still make that true.
      
      I wouldn't recommend serializing arbitrary open files under Python
      2 (for one thing, they can't trivially be deserialized in Python 3),
      but I didn't take any steps to prevent it either. Since this hasn't
      been possible, there shouldn't be code in the wild that is trying to
      do it---and it wouldn't be forward compatible with Python 3 either.
      be5a9d54
    • XeL64's avatar
      fix typo (#180) · b340b651
      XeL64 authored
      b340b651
  26. 25 Jul, 2017 2 commits