1. 27 Nov, 2007 1 commit
  2. 20 Nov, 2007 1 commit
  3. 17 Nov, 2007 5 commits
  4. 14 Nov, 2007 1 commit
  5. 10 Nov, 2007 7 commits
  6. 09 Nov, 2007 1 commit
  7. 07 Nov, 2007 2 commits
    • unknown's avatar
      Fix for bug #26447: "ALTER TABLE .. ORDER" does not work with InnoDB · 9c34fbfa
      unknown authored
      and auto_increment keys
      
      Problems: 
        1. ALTER TABLE ... ORDER BY... doesn't make sence if there's a 
           user-defined clustered index in the table.
        2. using a secondary index is slower than using a clustered one 
           for a table scan.
      
      Fixes:
        1. raise a warning.
        2. use the clustered index.
      
      
      mysql-test/include/mix1.inc:
        Fix for bug #26447: "ALTER TABLE .. ORDER" does not work with InnoDB 
        and auto_increment keys
          - test case.
      mysql-test/r/innodb.result:
        Fix for bug #26447: "ALTER TABLE .. ORDER" does not work with InnoDB 
        and auto_increment keys
          - results adjusted.
      mysql-test/r/innodb_mysql.result:
        Fix for bug #26447: "ALTER TABLE .. ORDER" does not work with InnoDB 
        and auto_increment keys
          - results adjusted.
      mysql-test/r/join_outer_innodb.result:
        Fix for bug #26447: "ALTER TABLE .. ORDER" does not work with InnoDB 
        and auto_increment keys
          - results adjusted.
      sql/sql_select.cc:
        Fix for bug #26447: "ALTER TABLE .. ORDER" does not work with InnoDB 
        and auto_increment keys
          - use the clustered index for a table scan (if any) as it's faster than
            using a secondary index.
      sql/sql_table.cc:
        Fix for bug #26447: "ALTER TABLE .. ORDER" does not work with InnoDB 
        and auto_increment keys
          - ALTER TABLE ... ORDER BY doesn't make sence if there's a 
            user-defined clustered index in the table. Ignore it in such cases
            and raise a warning.
      9c34fbfa
    • unknown's avatar
      Fix for bug #32137: prepared statement crash with str_to_date in update clause · dd780037
      unknown authored
      Problem: calling non-constant argument's val_xxx() methods 
      in the ::fix_length_and_dec() is inadmissible.
      
      Fix: call the method only for constant arguments.
      
      
      mysql-test/r/ps.result:
        Fix for bug #32137: prepared statement crash with str_to_date in update clause
          - test result.
      mysql-test/t/ps.test:
        Fix for bug #32137: prepared statement crash with str_to_date in update clause
          - test case.
      sql/item_timefunc.cc:
        Fix for bug #32137: prepared statement crash with str_to_date in update clause
          - call argument's val_str() only for constant items in the 
            Item_func_str_to_date::fix_length_and_dec().
      dd780037
  8. 06 Nov, 2007 3 commits
  9. 01 Nov, 2007 5 commits
  10. 31 Oct, 2007 8 commits
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-5.1-new-maint · c0f690b1
      unknown authored
      into  loke.(none):/home/knielsen/devel/mysql-5.1-new-maint
      
      c0f690b1
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-5.0-maint · 1c6a97e2
      unknown authored
      into  loke.(none):/home/knielsen/devel/mysql-5.0-maint
      
      1c6a97e2
    • unknown's avatar
      Merge loke.(none):/home/knielsen/devel/mysql-5.0-maint · a6ce0e21
      unknown authored
      into  loke.(none):/home/knielsen/devel/mysql-5.1-new-maint
      
      
      strings/ctype-simple.c:
        Auto merged
      strings/ctype-ucs2.c:
        SCCS merged
      a6ce0e21
    • unknown's avatar
      BUG#31799: Scrambled number output due to integer overflow · 0b023e98
      unknown authored
      An integer overflow in number->string conversion caused completely
      wrong output of the number LONGLONG_MIN with gcc 4.2.1.
      
      Fixed by eliminating the overflow, using only operations that are
      well-defined in ANSI C.
      
      
      strings/ctype-simple.c:
        An integer overflow in number->string conversion caused completely
        wrong output of the number LONGLONG_MIN with gcc 4.2.1.
        
        Fixed by eliminating the overflow, using only operations that are
        well-defined in ANSI C.
      strings/ctype-ucs2.c:
        An integer overflow in number->string conversion caused completely
        wrong output of the number LONGLONG_MIN with gcc 4.2.1.
        
        Fixed by eliminating the overflow, using only operations that are
        well-defined in ANSI C.
      strings/int2str.c:
        An integer overflow in number->string conversion caused completely
        wrong output of the number LONGLONG_MIN with gcc 4.2.1.
        
        Fixed by eliminating the overflow, using only operations that are
        well-defined in ANSI C.
      strings/longlong2str.c:
        An integer overflow in number->string conversion caused completely
        wrong output of the number LONGLONG_MIN with gcc 4.2.1.
        
        Fixed by eliminating the overflow, using only operations that are
        well-defined in ANSI C.
      0b023e98
    • unknown's avatar
      Merge mysql.com:/home/ram/work/mysql-5.1-maint · 1bfd921f
      unknown authored
      into  mysql.com:/home/ram/work/b30679/b30679.5.1
      
      
      client/mysqlcheck.c:
        Auto merged
      mysql-test/r/mysqlcheck.result:
        Auto merged
      mysql-test/t/mysqlcheck.test:
        Auto merged
      1bfd921f
    • unknown's avatar
      Merge mysql.com:/home/ram/work/mysql-5.1-maint · 18dc4af1
      unknown authored
      into  mysql.com:/home/ram/work/b30654/b30654.5.1
      
      
      client/mysqlcheck.c:
        Auto merged
      18dc4af1
    • unknown's avatar
      Merge mysql.com:/home/ram/work/mysql-5.0-maint · f4ee53fa
      unknown authored
      into  mysql.com:/home/ram/work/b30654/b30654.5.0
      
      f4ee53fa
    • unknown's avatar
      Merge mysql.com:/home/ram/work/b30654/b30654.5.0 · 79ac3982
      unknown authored
      into  mysql.com:/home/ram/work/b30654/b30654.5.1
      
      
      client/mysqlcheck.c:
        Auto merged
      mysql-test/r/mysqlcheck.result:
        Auto merged
      mysql-test/t/mysqlcheck.test:
        manual merge.
      79ac3982
  11. 30 Oct, 2007 1 commit
    • unknown's avatar
      Fix for bug #30654: mysqlcheck fails during upgrade of tables whose · ce18ce32
      unknown authored
      names include backticks or blank
      
      Problem: mysqlcheck doesn't escape backtick characters in the table names.
      
      Fix: escape them.
      
      
      client/mysqlcheck.c:
        Fix for bug #30654: mysqlcheck fails during upgrade of tables whose 
        names include backticks or blank
          - escape backtick characters in the table names.
      mysql-test/r/mysqlcheck.result:
        Fix for bug #30654: mysqlcheck fails during upgrade of tables whose 
        names include backticks or blank
          - test result.
      mysql-test/t/mysqlcheck.test:
        Fix for bug #30654: mysqlcheck fails during upgrade of tables whose 
        names include backticks or blank
          - test case.
      ce18ce32
  12. 29 Oct, 2007 5 commits