1. 08 Dec, 2016 2 commits
    • Sergei Golubchik's avatar
      MDEV-10713: signal 11 error on multi-table update - crash in... · 03dabfa8
      Sergei Golubchik authored
      MDEV-10713: signal 11 error on multi-table update - crash in handler::increment_statistics or in make_select or assertion failure pfs_thread == ((PFS_thread*) pthread_getspecific((THR_PFS)))
      
      Different fix. Don't allow Item_func_sp to be evaluated unless
      all tables are prelocked.
      
      Extend the test case to make sure Item_func_sp::val_str is called
      (the table must have at least one row for that).
      03dabfa8
    • Sergei Golubchik's avatar
      Revert "MDEV-10713: signal 11 error on multi-table update - crash in... · ab65db6d
      Sergei Golubchik authored
      Revert "MDEV-10713: signal 11 error on multi-table update - crash in handler::increment_statistics or in make_select or assertion failure pfs_thread == ((PFS_thread*) pthread_getspecific((THR_PFS)))"
      
      This reverts commit 035a5ac6.
      
      Two minor problems and one regression:
      1. caching the value in str_result. Other Item methods may use it,
         destroying the cache. See, for example, Item::save_in_field, where
         str_result is moved to use a local buffer (this failed main.grant)
      2. Item_func_conv_charset::safe is now set too late, it's initialized
         only in val_str() but checked before that, this failed many tests
         in optimized builds.
      
      to fix 1 - use tmp_result instead of str_result, to fix 2, use
      the else branch in the Item_func_conv_charset constructor to set
      safe purely from charset properties.
      
      But this introduces a regression, constant strings can no longer be
      converted, say, from utf8 to latin1 (because 'safe' will be false).
      This fails few tests too. There is no way to fix it without reverting
      the commit and converting constants, as before, in the constructor.
      ab65db6d
  2. 07 Dec, 2016 2 commits
  3. 06 Dec, 2016 4 commits
  4. 05 Dec, 2016 2 commits
    • Sergei Golubchik's avatar
      MDEV-10293 'setupterm' was not declared in this scope · 18cdff67
      Sergei Golubchik authored
      Check for readline before checking for curses headers, because
      MYSQL_CHECK_READLINE fails when curses is not found, but
      CHECK_INCLUDE_FILES simply remembers the fact and continues.  So if
      there's no curses, MYSQL_CHECK_READLINE will abort, the user will then
      installs curses and continue the build. Thus, CHECK_INCLUDE_HEADERS
      will remember that there is no curses, but other checks from
      MYSQL_CHECK_READLINE will remember that curses are there. It will
      result in inconsistent HAVE_xxx defines.
      18cdff67
    • Sergei Golubchik's avatar
      02d153c7
  5. 03 Dec, 2016 3 commits
  6. 28 Nov, 2016 1 commit
  7. 14 Nov, 2016 1 commit
  8. 12 Nov, 2016 1 commit
    • Igor Babaev's avatar
      Fixed bug mdev-11161. · 96b62b55
      Igor Babaev authored
      The flag TABLE_LIST::fill_me must be reset to false at the prepare
      phase for any materialized derived table used in the executed query.
      Otherwise if the optimizer decides to generate a key for such a table
      it is generated only for the first execution of the query.
      96b62b55
  9. 10 Nov, 2016 1 commit
  10. 03 Nov, 2016 1 commit
  11. 27 Oct, 2016 3 commits
  12. 17 Oct, 2016 2 commits
  13. 14 Oct, 2016 1 commit
  14. 13 Oct, 2016 6 commits
  15. 29 Sep, 2016 1 commit
  16. 28 Sep, 2016 3 commits
  17. 27 Sep, 2016 1 commit
  18. 26 Sep, 2016 5 commits