1. 03 Dec, 2015 2 commits
  2. 20 Nov, 2015 1 commit
  3. 18 Nov, 2015 2 commits
  4. 17 Nov, 2015 1 commit
  5. 09 Nov, 2015 2 commits
  6. 06 Nov, 2015 1 commit
    • Oleksandr Byelkin's avatar
      MDEV-8701 Crash on derived query · c88ca2c2
      Oleksandr Byelkin authored
      MDEV-8938 Server Crash on Update with joins
      
      Make unique table check after setup_fields of update because unique table can materialize table and we do not need field resolving after materialization.
      c88ca2c2
  7. 21 Oct, 2015 1 commit
  8. 11 Oct, 2015 1 commit
  9. 09 Oct, 2015 1 commit
    • Sergei Golubchik's avatar
      fixes for buildbot: · 16c4b3c6
      Sergei Golubchik authored
      * OSX (mysqlimport freeing unallocated memory)
      * Windows (didn't compile MSI)
      * fulltest2 (innodb crashes in --embedded --big)
      16c4b3c6
  10. 08 Oct, 2015 4 commits
  11. 06 Oct, 2015 5 commits
  12. 30 Sep, 2015 1 commit
  13. 29 Sep, 2015 1 commit
  14. 28 Sep, 2015 2 commits
  15. 27 Sep, 2015 2 commits
  16. 25 Sep, 2015 2 commits
  17. 24 Sep, 2015 2 commits
  18. 18 Sep, 2015 2 commits
  19. 07 Sep, 2015 1 commit
  20. 04 Sep, 2015 1 commit
  21. 26 Aug, 2015 1 commit
  22. 25 Aug, 2015 1 commit
  23. 21 Aug, 2015 1 commit
    • Arun Kuruvila's avatar
      Bug#20198490 : LOWER_CASE_TABLE_NAMES=0 ON WINDOWS LEADS TO · f4ff086a
      Arun Kuruvila authored
                     PROBLEMS
      
      Description:- Server variable "--lower_case_tables_names"
      when set to "0" on windows platform which does not support
      case sensitive file operations leads to problems. A warning
      message is printed in the error log while starting the
      server with "--lower_case_tables_names=0". Also according to
      the documentation, seting "lower_case_tables_names" to "0"
      on a case-insensitive filesystem might lead to index
      corruption.
      
      Analysis:- The problem reported in the bug is:-
      Creating an INNODB table 'a' and executing a query, "INSERT
      INTO a SELECT a FROM A;" on a server started with
      "--lower_case_tables_names=0" and running on a
      case-insensitive filesystem leads innodb to flat spin.
      Optimizer thinks that "a" and "A" are two different tables
      as the variable "lower_case_table_names" is set to "0". As a
      result, optimizer comes up with a plan which does not need a
      temporary table. If the same table is used in select and
      insert, a temporary table is needed. This incorrect
      optimizer plan leads to infinite insertions.
      
      Fix:- If the server is started with
      "--lower_case_tables_names" set to 0 on a case-insensitive
      filesystem, an error, "The server option
      'lower_case_table_names'is configured to use case sensitive
      table names but the data directory is on a case-insensitive
      file system which is an unsupported combination. Please
      consider either using a case sensitive file system for your
      data directory or switching to a case-insensitive table name
      mode.", is printed in the server error log and the server
      exits.
      f4ff086a
  24. 19 Aug, 2015 1 commit
  25. 18 Aug, 2015 1 commit
    • Shishir Jaiswal's avatar
      Bug #16171518 - LOAD XML DOES NOT HANDLE EMPTY ELEMENTS · ee02650b
      Shishir Jaiswal authored
      DESCRIPTION
      ===========
      Inability of mysql LOAD XML command to handle empty XML
      tags i.e. <row><tag/></row>. Also the behaviour is wrong
      and (different than above) when there is a space in empty
      tag i.e. <row><tag /></row>
      
      ANALYSIS
      ========
      In read_xml() the case where we encounter a close tag ('/')
      we're decreasing the 'level' blindly which is wrong.
      Actually when its an without-space-empty-tag (succeeding
      char is '>'), we need to skip the decrement. In other words
      whenever we hit a close tag ('/'), decrease the 'level'
      only when (i) It's not an (without space) empty tag i.e.
      <tag/> or, (ii) It is of format <row col="val" .../>
      
      FIX
      ===
      The switch case for '/' is modified. We've removed the
      blind decrement of 'level'. We do it only when its not an
      without-space-empty-tag. Also we are setting 'in_tag' to
      false to let program know that we're done reading current
      tag (required in the case of format <row col="val" .../>)
      ee02650b