1. 09 Feb, 2007 1 commit
    • unknown's avatar
      Bug#12122: The MERGE algorithm isn't applicable if the ORDER BY clause is · 308da651
      unknown authored
      present.
      
      A view created with CREATE VIEW ... ORDER BY ... cannot be resolved with
      the MERGE algorithm, even when no other part of the CREATE VIEW statement
      would require the view to be resolved using the TEMPTABLE algorithm.
      
      The check for presence of the ORDER BY clause in the underlying select is 
      removed from the st_lex::can_be_merged() function.
      The ORDER BY list of the underlying select is appended to the ORDER BY list 
      
      
      mysql-test/t/view.test:
        Added a test case for bug#12122: Views with ORDER BY can't be resolved using MERGE algorithm.
      mysql-test/r/view.result:
        Added a test case for bug#12122: Views with ORDER BY can't be resolved using MERGE algorithm.
      sql/sql_lex.cc:
        Bug#12122: Views with ORDER BY can't be resolved using MERGE algorithm.
        The st_lex::can_be_merged() function now allows views with the ORDER BY
        clause to be resolved using MERGE algorithm. The ORDER BY list of the view 
        is appended to the ORDER BY list of the embedding select.
      308da651
  2. 08 Feb, 2007 3 commits
  3. 07 Feb, 2007 8 commits
    • unknown's avatar
      Fixed bug #25931. · 3609c3a4
      unknown authored
      View check option clauses were ignored for updates of multi-table
      views when the updates could not be performed on fly and the rows
      to update had to be put into temporary tables first.
      
      
      
      mysql-test/r/view.result:
        Added a test case for bug #25931.
      mysql-test/t/view.test:
        Added a test case for bug #25931.
        Adjusted another existed test case to have the correct result.
      sql/sql_update.cc:
        Fixed bug #25931.
        View check option clauses were ignored for updates of multi-table
        views when the updates could not be performed on fly and the rows
        to update had to be put into temporary tables first.
        Added the required check to multi_update::do_updates to fix the problem.
      3609c3a4
    • unknown's avatar
      Merge tulin@bk-internal.mysql.com:/home/bk/mysql-4.1 · 75d614e0
      unknown authored
      into  poseidon.mysql.com:/home/tomas/mysql-4.1-ndb
      
      
      75d614e0
    • unknown's avatar
      Merge tulin@bk-internal.mysql.com:/home/bk/mysql-5.0 · 1daa0e44
      unknown authored
      into  poseidon.mysql.com:/home/tomas/mysql-5.0-ndb
      
      
      sql/ha_ndbcluster.cc:
        Auto merged
      1daa0e44
    • unknown's avatar
      Merge mskold@bk-internal.mysql.com:/home/bk/mysql-5.0-ndb · a11fb9eb
      unknown authored
      into  mysql.com:/windows/Linux_space/MySQL/mysql-5.0-ndb
      
      
      a11fb9eb
    • unknown's avatar
      Merge mysql.com:/windows/Linux_space/MySQL/mysql-5.0 · 7d678ab9
      unknown authored
      into  mysql.com:/windows/Linux_space/MySQL/mysql-5.0-ndb
      
      
      ndb/include/ndbapi/NdbIndexScanOperation.hpp:
        Auto merged
      ndb/include/ndbapi/NdbScanOperation.hpp:
        Auto merged
      ndb/src/ndbapi/NdbScanOperation.cpp:
        Auto merged
      sql/ha_ndbcluster.cc:
        Auto merged
      sql/ha_ndbcluster.h:
        Auto merged
      7d678ab9
    • unknown's avatar
      NdbScanOperation.hpp, NdbScanOperation.cpp, ha_ndbcluster.cc: · c8f470ea
      unknown authored
        bug#25821  Excessive partition pruning for multi-range index scan in NDB API: added multi_range error checking in end_of_bound
      ha_ndbcluster.h:
        Removed stray mthod declaration
      
      
      sql/ha_ndbcluster.h:
        Removed stray mthod declaration
      ndb/include/ndbapi/NdbScanOperation.hpp:
        bug#25821  Excessive partition pruning for multi-range index scan in NDB API: added multi_range error checking in end_of_bound
      ndb/src/ndbapi/NdbScanOperation.cpp:
        bug#25821  Excessive partition pruning for multi-range index scan in NDB API: added multi_range error checking in end_of_bound
      sql/ha_ndbcluster.cc:
        bug#25821  Excessive partition pruning for multi-range index scan in NDB API: added multi_range error checking in end_of_bound
      c8f470ea
    • unknown's avatar
      bug#25821 Excessive partition pruning for multi-range index scan in NDB API:... · f3463a8c
      unknown authored
      bug#25821  Excessive partition pruning for multi-range index scan in NDB API: post-review fix, added default value
      
      
      
      f3463a8c
    • unknown's avatar
      Fixed bug #26124: SELECT from a view wrapper over a table · 3a54e593
      unknown authored
      with a column of the DATETIME type could return a wrong 
      result set if the WHERE clause included a BETWEEN condition
      on the column.
      Fixed the method Item_func_between::fix_length_and_dec
      where the aggregation type for BETWEEN predicates calculated
      incorrectly if the first argument was a view column of the
      DATETIME type.
      
      
      mysql-test/r/view.result:
        Added a test case for bug #26124.
      mysql-test/t/view.test:
        Added a test case for bug #26124.
      3a54e593
  4. 06 Feb, 2007 3 commits
    • unknown's avatar
      Fix for bug#25821 Excessive partition pruning for multi-range index scan in... · ba8a684d
      unknown authored
      Fix for bug#25821  Excessive partition pruning for multi-range index scan in NDB API: don't set distribution key if multi_range
      
      
      
      ba8a684d
    • unknown's avatar
      Bug#19978: INSERT .. ON DUPLICATE erroneously reports some records were · 976f0a39
      unknown authored
      updated.
      
      INSERT ... ON DUPLICATE KEY UPDATE reports that a record was updated when
      the duplicate key occurs even if the record wasn't actually changed
      because the update values are the same as those in the record.
      
      Now the compare_record() function is used to check whether the record was
      changed and the update of a record reported only if the record differs
      from the original one.
      
      
      sql/sql_update.cc:
        Bug#19978: INSERT .. ON DUPLICATE erroneously reports some records were
        updated.
        The compare_record() function was changed to non-static one.
      sql/sql_insert.cc:
        Bug#19978: INSERT .. ON DUPLICATE erroneously reports some records were
        updated.
        Now the compare_record() function is used to check whether the record was
        changed and the update of a record reported only if the record differs
        from the original one.
      sql/mysql_priv.h:
        Bug#19978: INSERT .. ON DUPLICATE erroneously reports some records were
        updated.
        Added the prototype of the compare_record() function.
      mysql-test/t/insert_select.test:
        Added a test case for bug#19978: INSERT .. ON DUPLICATE erroneously reports
        some records were updated.
      mysql-test/r/insert_select.result:
        Added a test case for bug#19978: INSERT .. ON DUPLICATE erroneously reports
        some records were updated.
      976f0a39
    • unknown's avatar
      Bug #22344: InnoDB keys act strange on datetime vs timestamp comparison · c35ceeca
      unknown authored
       Ignoring error codes from type conversion allows default (wrong) values to
       go unnoticed in the formation of index search conditions.
       Fixed by correctly checking for conversion errors.
      
      
      mysql-test/r/select.result:
        Bug #22344: InnoDB keys act strange on datetime vs timestamp comparison
         - test case
      mysql-test/t/select.test:
        Bug #22344: InnoDB keys act strange on datetime vs timestamp comparison
         - test case
      sql/field.h:
        Bug #22344: InnoDB keys act strange on datetime vs timestamp comparison
         - don't ignore coversion errors
      sql/field_conv.cc:
        Bug #22344: InnoDB keys act strange on datetime vs timestamp comparison
         - don't ignore coversion errors
      sql/item.cc:
        Bug #22344: InnoDB keys act strange on datetime vs timestamp comparison
         - don't ignore coversion errors
      c35ceeca
  5. 05 Feb, 2007 1 commit
    • unknown's avatar
      Test and bug fixes and removed unneccessary files. · 9946ed16
      unknown authored
      
      mysys/my_getopt.c:
        Fixes problem with getting output lines from
        my_getopt in random places in tests.
      sql/sql_prepare.cc:
        Fixes problem with failing mysql_client_test
        on some machines. This is actually a problem
        with prepared statements.
      9946ed16
  6. 03 Feb, 2007 2 commits
  7. 02 Feb, 2007 11 commits
    • unknown's avatar
      Fix bug #24035. · e0d8e8fd
      unknown authored
      This performance degradation for UPDATEs could be observed in the update
      statements for which the search key cannot be converted to any valid
      value of the type of the search column, like for a  the condition
      int_fld=99999999999999999999999999, though it can be guaranteed here
      that there is no row with such a key value. 
      
      
      mysql-test/r/update.result:
        Added a test case for bug #24035.
      mysql-test/t/update.test:
        Added a test case for bug #24035.
      sql/opt_range.cc:
        Fix bug #24035.
        This performance degradation for could be observed in the update
        statements for which the search key cannot be converted to any valid
        value of the type of the search column, like for a  the condition
        int_fld=99999999999999999999999999, though it can be guaranteed here
        that there is no row with such a key value. 
        Now the function get_mm_leaf creates trees of the type SEL_ARG::IMPOSSIBLE 
        for such conditions that tells the range scan not to perform any search
        at all.
      e0d8e8fd
    • unknown's avatar
      Merge chilla.local:/home/mydev/mysql-4.1-axmrg · 8a9c521b
      unknown authored
      into  chilla.local:/home/mydev/mysql-5.0-axmrg
      
      
      sql/handler.cc:
        Auto merged
      sql/examples/ha_tina.cc:
        Auto merged
      sql/examples/ha_tina.h:
        Auto merged
      sql/mysqld.cc:
        Auto merged
      mysql-test/Makefile.am:
        Manual merged
      8a9c521b
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 3c0aca02
      unknown authored
      into  chilla.local:/home/mydev/mysql-5.0-axmrg
      
      
      sql/item_func.cc:
        Auto merged
      3c0aca02
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.1 · 0dc19dad
      unknown authored
      into  chilla.local:/home/mydev/mysql-4.1-axmrg
      
      
      0dc19dad
    • unknown's avatar
      After merge fix · 98b9ac69
      unknown authored
      98b9ac69
    • unknown's avatar
      04cbadde
    • unknown's avatar
      Merge mysql.com:/home/gluh/MySQL/Merge/5.0 · 9bb750f5
      unknown authored
      into  mysql.com:/home/gluh/MySQL/Merge/5.0-opt
      
      
      9bb750f5
    • unknown's avatar
      Valgrind errors · 84445bbb
      unknown authored
      added valgrind.supp to EXTRA_SCRIPTS(for pushbuild)
      
      
      84445bbb
    • unknown's avatar
      Merge lzhou@bk-internal.mysql.com:/home/bk/mysql-5.0-ndb · 61aee35c
      unknown authored
      into  dev3-63.(none):/home/zhl/mysql/tree-merge/5.0/mysql-5.0-ndb
      
      
      61aee35c
    • unknown's avatar
      Merge chilla.local:/home/mydev/mysql-4.1-axmrg · d03d2987
      unknown authored
      into  chilla.local:/home/mydev/mysql-5.0-axmrg
      
      
      include/my_pthread.h:
        Auto merged
      include/thr_alarm.h:
        Auto merged
      mysys/my_pthread.c:
        Auto merged
      mysys/my_thr_init.c:
        Auto merged
      d03d2987
    • unknown's avatar
      After merge fix · 5305cd7c
      unknown authored
      5305cd7c
  8. 01 Feb, 2007 11 commits