1. 21 Apr, 2017 1 commit
    • Sachin Setiya's avatar
      Fix BuildBot Failure. · 85f53e46
      Sachin Setiya authored
      In some slave like p8-xenial-bintar-debug we are using C90 standard
      which does not allow declaration and code to be mixed.
      85f53e46
  2. 20 Apr, 2017 1 commit
  3. 18 Apr, 2017 7 commits
  4. 11 Apr, 2017 1 commit
  5. 07 Apr, 2017 1 commit
  6. 05 Apr, 2017 2 commits
  7. 04 Apr, 2017 1 commit
    • Igor Babaev's avatar
      Fixed the bug mdev-12429 and its duplicates mdev-12145 and mdev-9886. · b0395d87
      Igor Babaev authored
      Also fixed a wrong result for a test case for mdev-7691
      (the alternative one).
      The test  cases for all these bug have materialized semi-joins used
      inside dependent sub-queries.
      
      The patch actually reverts the change inroduced by Monty in 2003.
      It looks like this change is not valid anymore after the implementation
      of semi-joins.
      Adjusted output from EXPLAIN for many other test cases.
      b0395d87
  8. 24 Mar, 2017 1 commit
  9. 21 Mar, 2017 1 commit
  10. 18 Mar, 2017 1 commit
    • Bharathy Satish's avatar
      Bug #25717383: MYSQLDUMP MAY EXECUTE ANY ARBITRARY QUERY · 6fa5e081
      Bharathy Satish authored
      While writing comments if database object names has a new
      line character, then next line is considered a command, rather
      than a comment.
      This patch fixes the way comments are constructed in mysqldump.
      
      (cherry picked from commit 1099f9d17b1c697c2760f86556f5bae7d202b444)
      6fa5e081
  11. 17 Mar, 2017 1 commit
  12. 14 Mar, 2017 2 commits
  13. 13 Mar, 2017 1 commit
  14. 12 Mar, 2017 1 commit
  15. 10 Mar, 2017 2 commits
  16. 09 Mar, 2017 1 commit
  17. 08 Mar, 2017 6 commits
  18. 06 Mar, 2017 1 commit
  19. 05 Mar, 2017 1 commit
  20. 03 Mar, 2017 1 commit
    • Marko Mäkelä's avatar
      MDEV-11520: Retry posix_fallocate() after EINTR. · 6b8173b6
      Marko Mäkelä authored
      The function posix_fallocate() as well as the Linux system call
      fallocate() can return EINTR when the operation was interrupted
      by a signal. In that case, keep retrying the operation, except
      if InnoDB shutdown has been initiated.
      6b8173b6
  21. 28 Feb, 2017 1 commit
  22. 27 Feb, 2017 5 commits
    • Igor Babaev's avatar
      Fixed bug mdev-12099. · 5a0fff50
      Igor Babaev authored
      The function mysql_derived_merge() erroneously did not mark newly formed
      AND formulas in ON conditions with the flag abort_on_null. As a result
      not_null_tables() calculated incorrectly for these conditions. This
      could prevent conversion of embedded outer joins into inner joins.
      
      Changed a test case from table_elim.test to preserve the former execution
      plan.
      5a0fff50
    • Sergei Golubchik's avatar
      MDEV-5999 MySQL Bug#12766319 - 61865: RENAME USER DOES NOT WORK CORRECTLY -... · 199f88cb
      Sergei Golubchik authored
      MDEV-5999 MySQL Bug#12766319 - 61865: RENAME USER DOES NOT WORK CORRECTLY - REQUIRES FLUSH PRIVILEGES
      
      use update_hostname() to update the hostname.
      test case comes from
      
        commit 0abdeed1d6d
        Author: gopal.shankar@oracle.com <>
        Date:   Thu Mar 29 00:20:54 2012 +0530
      
          Bug#12766319 - 61865: RENAME USER DOES NOT WORK CORRECTLY -
                                REQUIRES FLUSH PRIVILEGES
      199f88cb
    • Dmitry Lenev's avatar
      Fix for bug#11759114 - '51401: GRANT TREATS NONEXISTENT · 494a9415
      Dmitry Lenev authored
      FUNCTIONS/PRIVILEGES DIFFERENTLY'.
      
      The problem was that attempt to grant EXECUTE or ALTER
      ROUTINE privilege on stored procedure which didn't exist
      succeed instead of returning an appropriate error like
      it happens in similar situation for stored functions or
      tables.
      
      The code which handles granting of privileges on individual
      routine calls sp_exist_routines() function to check if routine
      exists and assumes that the 3rd parameter of the latter
      specifies whether it should check for existence of stored
      procedure or function. In practice, this parameter had
      completely different meaning and, as result, this check was
      not done properly for stored procedures.
      
      This fix addresses this problem by bringing sp_exist_routines()
      signature and code in line with expectation of its caller.
      494a9415
    • Sergei Golubchik's avatar
      delete the installation warning for CentOS4/RHEL4 · 0a480f03
      Sergei Golubchik authored
      it went out of support five years ago
      0a480f03
    • Sergei Golubchik's avatar