1. 24 Nov, 2010 1 commit
  2. 23 Nov, 2010 1 commit
  3. 24 Nov, 2010 7 commits
  4. 23 Nov, 2010 2 commits
    • Sergey Glukhov's avatar
      5.1-bugteam->5.5-bugteam merge · ee2b9394
      Sergey Glukhov authored
      ee2b9394
    • Sergey Glukhov's avatar
      Bug#56862 Execution of a query that uses index merge returns a wrong result · 7704e3c2
      Sergey Glukhov authored
      In case of low memory sort buffer QUICK_INDEX_MERGE_SELECT creates
      temporary file where is stores row ids which meet QUICK_SELECT ranges
      except of clustered pk range, clustered range is processed separately.
      In init_read_record we check if temporary file is used and choose
      appropriate record access method. It does not take into account that
      temporary file contains partial result in case of QUICK_INDEX_MERGE_SELECT
      with clustered pk range.
      The fix is always to use rr_quick if QUICK_INDEX_MERGE_SELECT
      with clustered pk range is used.
      7704e3c2
  5. 22 Nov, 2010 10 commits
  6. 20 Nov, 2010 1 commit
    • Davi Arnaut's avatar
      WL#5665: Removal of the autotools-based build system · 5324d10f
      Davi Arnaut authored
      Remove some more leftovers from the initial removal:
      
      o Update relevant mentions of configure.in throughout
      the source code.
      
      o Remove win/configure.js, which at this point just
      duplicates logic already present in CMake based build
      system.
      
      o Remove support files which relied on the autotools
      build system. In any case, MySQL is no longer officially
      supported on SCO.
      
      o Remove files which are no longer part of the build.
      5324d10f
  7. 22 Nov, 2010 1 commit
  8. 21 Nov, 2010 1 commit
  9. 20 Nov, 2010 3 commits
    • Davi Arnaut's avatar
      WL#5665: Removal of the autotools-based build system · f6deb00a
      Davi Arnaut authored
      The autotools-based build system has been superseded and
      is being removed in order to ease the maintenance burden on
      developers tweaking and maintaining the build system.
      
      In order to support tools that need to extract the server
      version, a new file that (only) contains the server version,
      called VERSION, is introduced. The file contents are human
      and machine-readable. The format is:
      
      MYSQL_VERSION_MAJOR=5
      MYSQL_VERSION_MINOR=5
      MYSQL_VERSION_PATCH=8
      MYSQL_VERSION_EXTRA=-rc
      
      The CMake based version extraction in cmake/mysql_version.cmake
      is changed to extract the version from this file. The configure
      to CMake wrapper is retained for backwards compatibility and to
      support the BUILD/ scripts. Also, a new a makefile target
      show-dist-name that prints the server version is introduced.
      f6deb00a
    • Davi Arnaut's avatar
      e1cba38b
    • Davi Arnaut's avatar
      Bug#57994: Compiler flag change build error : my_redel.c · 871930e7
      Davi Arnaut authored
      Although ICC identifies itself as GCC, even in version numbers,
      it does not support the stpcpy built-in.
      871930e7
  10. 19 Nov, 2010 13 commits
    • Vladislav Vaintroub's avatar
      ece6212f
    • Vladislav Vaintroub's avatar
      merge · 2cf7ab15
      Vladislav Vaintroub authored
      2cf7ab15
    • Vladislav Vaintroub's avatar
      Bug#58313: CMake stops with VS Express if -DBUILD_CONFIG=mysql_release.cmake · bf6a7d09
      Vladislav Vaintroub authored
      Bug : -DBUILD_CONFIG=mysql_release sets SIGNCODE parameter which requires 
      singtool.exe (part of Windows SDK)  in order to be able to sign the binaries (
      only if valid certificate is found). However singtool is not a part of the SDK shipped
      with Visual Studio Express, so the build fails claiming missing singtools.exe
      
      Fix: Do not  use SIGNCODE  wiith VC Express.
      
      Also, fix broken nmake build (*.rc files could not be compiled due to ADD_DEFINITIONS
      contaning C/C++ compiler specific flags)
      bf6a7d09
    • Alexander Barkov's avatar
      Bug#58190 BETWEEN no longer uses indexes for date or datetime fields · 77c098a7
      Alexander Barkov authored
      Regression introduced by WL#2649.
      
      Problem: queries with date/datetime columns did not use indexes:
      set names non_latin1_charset;
      select * from date_index_test
      where date_column between '2010-09-01' and '2010-10-01';
      
      before WL#2649 indexes worked fine because charset of 
      date/datetime
      columns was BINARY which always won.
      
      Fix: testing that collation of the operation matches collation 
      of the field is only needed in case of "real" string data types.
      For DATE, DATETIME it's not needed.
      
      
        @ mysql-test/include/ctype_numconv.inc
        @ mysql-test/r/ctype_binary.result
        @ mysql-test/r/ctype_cp1251.result
        @ mysql-test/r/ctype_latin1.result
        @ mysql-test/r/ctype_ucs.result
        @ mysql-test/r/ctype_utf8.result
        Adding tests
      
        @ sql/field.h
        Adding new method Field_str::match_collation_to_optimize_range()
        for use in opt_range.cc to distinguish between
        "real string" types like CHAR, VARCHAR, TEXT
        (Field_string, Field_varstring, Field_blob)
      
        and "almost string" types DATE, TIME, DATETIME
        (Field_newdate, Field_datetime, Field_time, Field_timestamp)
      
        @ sql/opt_range.cc
        Using new method instead of checking result_type() against STRING result.
      
      Note:
      
        Another part of this problem (which is not regression) 
        is submitted separately (see bug##58329).
      77c098a7
    • Alexander Barkov's avatar
      Bug#58175 xml functions read initialized bytes when conversions happen · 677639f4
      Alexander Barkov authored
      Problem:
      
       nr_of_decimals could read behind the end of the buffer
       in case of a non-null-terminated string, which caused
       valgring warnings.
      
      Fix:
      
        fixing nr_of_decimals not to read behind the "end" pointer.
      
      modified:
      
        @ mysql-test/r/xml.result
        @ mysql-test/t/xml.test
        @ sql/item.cc
      677639f4
    • Georgi Kodinov's avatar
      Bug #58119: Typo in warning on log: [Warning] 'proxes_priv' entry · 1ab1cb8a
      Georgi Kodinov authored
      Fixed a typo in an error message.
      1ab1cb8a
    • Vladislav Vaintroub's avatar
      merge · e2fb2141
      Vladislav Vaintroub authored
      e2fb2141
    • Sunanda Menon's avatar
    • Dmitry Lenev's avatar
      Fix tree name which was accidentally changed · 41af8df7
      Dmitry Lenev authored
      during the merge.
      41af8df7
    • Dmitry Lenev's avatar
      Merged recent change from mysql-5.5-bugteam into · 8d0eabd2
      Dmitry Lenev authored
      mysql-5.5-runtime tree.
      8d0eabd2
    • Dmitry Lenev's avatar
      Suppress false-positive uninitialized variable use · 4ca561e7
      Dmitry Lenev authored
      warnings in Event_queue::get_top_for_execution_if_time()
      method which has caused -Werror build to fail.
      4ca561e7
    • Dmitry Lenev's avatar
      Fix for bug #57985 "ONLINE/FAST ALTER PARTITION can fail and · b019ba2f
      Dmitry Lenev authored
      leave the table unusable".
       
      Failing ALTER statement on partitioned table could have left
      this table in an unusable state. This has happened in cases
      when ALTER was executed using "fast" algorithm, which doesn't 
      involve copying of data between old and new versions of table, 
      and the resulting new table was incompatible with partitioning
      function in some way.
       
      The problem stems from the fact that discrepancies between new 
      table definition and partitioning function are discovered only 
      when the table is opened. In case of "fast" algorithm this has
      happened too late during ALTER's execution, at the moment when
      all changes were already done and couldn't have been reverted.
       
      In the cases when "slow" algorithm, which copies data, is used 
      such discrepancies are detected at the moment new table
      definition is opened implicitly when new version of table is
      created in storage engine. As result ALTER is aborted before 
      any changes to table were done.
       
      This fix tries to address this issue by ensuring that "fast"
      algorithm behaves similarly to "slow" algorithm and checks
      compatibility between new definition and partitioning function 
      by trying to open new definition after .FRM file for it has 
      been created.
       
      Long term we probably should implement some way to check
      compatibility between partitioning function and new table
      definition which won't involve opening it, as this should
      allow much cleaner fix for this problem.
      b019ba2f
    • Alexander Barkov's avatar
      Bug#57306 SHOW PROCESSLIST does not display string literals well. · bdfcad0f
      Alexander Barkov authored
      A post-patch fixing test failures on Windows.
      
      Host name in "SHOW PROCESSLIST" is displayed with port number
      for some reasons.
      bdfcad0f