1. 20 Nov, 2012 2 commits
    • unknown's avatar
      Merge MariaDB 5.1->5.2. · cbae2943
      unknown authored
      cbae2943
    • unknown's avatar
      MDEV-3861: assertions in TC_LOG_MMAP. · 47c5018f
      unknown authored
      Fix some problems in the TC_LOG_MMAP commit processing, which could
      lead to assertions in some cases.
      
      Problems are mostly reproducible in MariaDB 10.0 with asynchroneous
      commit checkpoints, but most of the problems were present in earlier
      versions also.
      47c5018f
  2. 19 Nov, 2012 1 commit
  3. 17 Nov, 2012 1 commit
  4. 12 Nov, 2012 1 commit
  5. 10 Nov, 2012 2 commits
    • Vladislav Vaintroub's avatar
      MDEV-3849 - 1 bytes stack overwrite in normalize_dirname(). · 35313020
      Vladislav Vaintroub authored
      Take into account that length of strings passed down to this function can be up to FN_REFLEN+1 bytes. including terminating zero.
      The overwrite was caused by incomplete fix to MySQL Bug # 44834
      35313020
    • Igor Babaev's avatar
      Fixed bug mdev-3845. · 094f4cf7
      Igor Babaev authored
      If triggers are used for an insert/update/delete statement than the values of
      all virtual columns must be computed as any of them may be used by the triggers.
      094f4cf7
  6. 09 Nov, 2012 3 commits
  7. 08 Nov, 2012 3 commits
  8. 07 Nov, 2012 1 commit
  9. 06 Nov, 2012 1 commit
  10. 02 Nov, 2012 1 commit
  11. 01 Nov, 2012 3 commits
  12. 31 Oct, 2012 4 commits
  13. 09 Oct, 2012 1 commit
  14. 14 Oct, 2012 1 commit
  15. 02 Oct, 2012 1 commit
  16. 27 Sep, 2012 2 commits
  17. 26 Sep, 2012 3 commits
  18. 25 Sep, 2012 1 commit
  19. 26 Sep, 2012 1 commit
  20. 24 Sep, 2012 2 commits
  21. 14 Sep, 2012 1 commit
    • unknown's avatar
      Fix bug lp:1009187, mdev-373, mysql bug#58628 · b917fb63
      unknown authored
      Analysis:
      The queries in question use the [unique | index]_subquery execution methods.
      These methods reuse the ref keys constructed by create_ref_for_key(). The
      way create_ref_for_key() works is that it doesn't store in ref.key_copy[]
      store_key elements that represent constants. In particular it doesn't store
      the store_key for NULL constants.
      
      The execution of [unique | index]_subquery calls
      subselect_uniquesubquery_engine::copy_ref_key, which in addition to copy
      the left IN argument into a index lookup key, is supposed to detect if
      the left IN argument contains NULLs. Since the store_key for the NULL
      constant is not copied into the key array, the null is not detected, and
      execution erroneously proceeds as if it should look for a complete match.
      
      Solution:
      The solution (unlike MySQL) is to reuse already computed information about
      NULL presence. Item_in_optimizer::val_int already finds out if the left IN
      operand contains NULLs. The fix propagates this to the execution methods
      subselect_[unique | index]subquery_engine::exec so it knows if there were
      NULL values independent of the presence of keys.
      
      In addition the patch siplifies copy_ref_key() and the logic that hanldes
      the case of NULLs in the left IN operand.
      b917fb63
  22. 11 Sep, 2012 1 commit
  23. 05 Sep, 2012 1 commit
  24. 03 Sep, 2012 1 commit
  25. 31 Aug, 2012 1 commit
    • Annamalai Gurusami's avatar
      Bug #13453036 ERROR CODE 1118: ROW SIZE TOO LARGE - EVEN · f3a6816f
      Annamalai Gurusami authored
      THOUGH IT IS NOT.
      
      The following error message is misleading because it claims 
      that the BLOB space is not counted.  
      
      "ERROR 1118 (42000): Row size too large. The maximum row size for 
      the used table type, not counting BLOBs, is 8126. You have to 
      change some columns to TEXT or BLOBs"
      
      When the ROW_FORMAT=compact or ROW_FORMAT=REDUNDANT is used,
      the BLOB prefix is stored inline along with the row.  So 
      the above error message is changed as follows depending on
      the row format used:
      
      For ROW_FORMAT=COMPRESSED or ROW_FORMAT=DYNAMIC, the error
      message is as follows:
      
      "ERROR 42000: Row size too large (> 8126). Changing some
      columns to TEXT or BLOB may help. In current row format, 
      BLOB prefix of 0 bytes is stored inline."
      
      For ROW_FORMAT=COMPACT or ROW_FORMAT=REDUNDANT, the error
      message is as follows:
      
      "ERROR 42000: Row size too large (> 8126). Changing some
      columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or 
      ROW_FORMAT=COMPRESSED may help. In current row
      format, BLOB prefix of 768 bytes is stored inline."
      
      rb://1252 approved by Marko Makela
      f3a6816f