An error occurred fetching the project authors.
  1. 11 May, 2018 1 commit
    • Sergey Vojtovich's avatar
      MDEV-15592 - Column COMPRESSED should select a 'high order' datatype · c9829242
      Sergey Vojtovich authored
      Compressed blob columns didn't accept data at their capacity. E.g. storing
      255 bytes to TINYBLOB results in "Data too long" error.
      
      Now it is allowed assuming compression method was able to produce shorter
      string (so that both metadata and compressed data fits blob) and
      column_compression_threshold is lower than blob.
      
      If no compression was performed, we still have to reserve additional byte
      for metadata and thus we perform normal data truncation and return it's
      status.
      c9829242
  2. 10 May, 2018 1 commit
  3. 30 Apr, 2018 1 commit
  4. 20 Apr, 2018 2 commits
  5. 02 Apr, 2018 1 commit
  6. 29 Mar, 2018 1 commit
  7. 31 Aug, 2017 1 commit
    • Sergey Vojtovich's avatar
      MDEV-11371 - column compression · fdc47792
      Sergey Vojtovich authored
      Storage engine independent support for column compression.
      
      TINYBLOB, BLOB, MEDIUMBLOB, LONGBLOB, TINYTEXT, TEXT, MEDIUMTEXT, LONGTEXT,
      VARCHAR and VARBINARY columns can be compressed.
      
      New COMPRESSED column attribute added:
      COMPRESSED[=<compression_method>]
      
      System variables added:
      column_compression_threshold
      column_compression_zlib_level
      column_compression_zlib_strategy
      column_compression_zlib_wrap
      
      Status variables added:
      Column_compressions
      Column_decompressions
      
      Limitations:
      - the only supported method currently is zlib
      - CSV storage engine stores data uncompressed on-disk even if COMPRESSED
        attribute is present
      - it is not possible to create indexes over compressed columns.
      fdc47792