An error occurred fetching the project authors.
  1. 09 Sep, 2009 1 commit
    • Sergey Vojtovich's avatar
      BUG#29203 - archive tables have weird values in show table status · f22baa9a
      Sergey Vojtovich authored
      Archive engine returns wrong values for average record length
      and max data length.
      
      With this fix they're calculated as following:
      - max data length is 2 ^ 63 where large files are supported
        and INT_MAX32 where this is not supported;
      - average record length is data length / records in data file.
      f22baa9a
  2. 26 Mar, 2009 1 commit
  3. 18 Mar, 2009 1 commit
    • Satya B's avatar
      Fix for BUG#32880 - Repairing Archive table fails with internal error 144 · bbd694a3
      Satya B authored
      Any statement reading corrupt archive data file
      (CHECK/REPAIR/SELECT/UPDATE/DELETE) may cause assertion
      failure in debug builds. This assertion has been removed
      and an error is returned instead.
      
      Also fixed that CHECK/REPAIR returns vague error message
      when it mets corruption in archive data file. This is
      fixed by returning proper error code.
      bbd694a3
  4. 14 Mar, 2008 1 commit
  5. 06 Dec, 2007 1 commit
  6. 27 Nov, 2007 2 commits
  7. 23 Nov, 2007 1 commit
  8. 26 Oct, 2007 1 commit
  9. 22 Sep, 2007 1 commit
  10. 21 Sep, 2007 1 commit
  11. 28 Jun, 2007 1 commit
  12. 27 Jun, 2007 1 commit
  13. 31 Mar, 2007 1 commit
  14. 30 Mar, 2007 1 commit
    • svoj@mysql.com/june.mysql.com's avatar
      BUG#26138 - REPAIR TABLE with option USE_FRM erases all records in · 556de62f
      svoj@mysql.com/june.mysql.com authored
                  ARCHIVE table
      ARCHIVE table was truncated by REPAIR TABLE ... USE_FRM statement.
      The table handler returned its file name extensions in a wrong order.
      REPAIR TABLE believed it has to use the meta file to create a new table
      from it.
      
      With the fixed order, REPAIR TABLE does now use the data file to create
      a new table. So REPAIR TABLE ... USE_FRM works well with ARCHIVE engine
      now.
      
      This issue affects 5.0 only, since in 5.1 ARCHIVE engine stores meta
      information and data in the same file.
      556de62f
  15. 26 Jan, 2007 3 commits
  16. 11 Dec, 2006 1 commit
  17. 02 Dec, 2006 1 commit
  18. 16 Nov, 2006 1 commit
  19. 06 Jul, 2006 1 commit
  20. 18 May, 2006 1 commit
  21. 15 May, 2006 1 commit
  22. 17 Apr, 2006 1 commit
  23. 22 Feb, 2006 1 commit
  24. 15 Feb, 2006 1 commit
    • brian@zim.tangent.org's avatar
      This patch adds a new field to the meta file for tracking flushes (this is... · d5643042
      brian@zim.tangent.org authored
      This patch adds a new field to the meta file for tracking flushes (this is being kept to later do stats and determine how often the compression buffer is being foiled). This should keep things all nice an compatible between versions.
      Also added a flush table test as well. Found one possible bug in OPTIMIZE TABLE which has never been reported, but I think it would be possible on a file system that ran out of disk.
      d5643042
  25. 08 Feb, 2006 1 commit
  26. 13 Jan, 2006 1 commit
  27. 11 Jan, 2006 1 commit
  28. 10 Jan, 2006 1 commit
  29. 26 Oct, 2005 1 commit
  30. 18 Oct, 2005 1 commit
  31. 30 Aug, 2005 1 commit
  32. 29 Aug, 2005 1 commit
  33. 11 Jul, 2005 1 commit
  34. 28 Apr, 2005 1 commit
  35. 27 Apr, 2005 2 commits
  36. 26 Apr, 2005 1 commit