1. 03 Feb, 2006 1 commit
  2. 01 Feb, 2006 2 commits
    • unknown's avatar
      fix for bug #12744 (MYSQL_STMT operations cause seg fault after connection reset) · 1e686ae7
      unknown authored
      
      libmysql/libmysql.c:
        stmt->mysql could be 0x0 if the connection has failed between prepare and execute
        or any other operation. thus if the user decides to use mysql_stmt_reset()
        we should not segfault.
      tests/mysql_client_test.c:
        test for bug #12744 (MYSQL_STMT operations cause seg fault after connection reset)
      1e686ae7
    • unknown's avatar
      FIxed bug #14927. · a400e7fe
      unknown authored
      A query with a group by and having clauses could return a wrong
      result set if the having condition contained a constant conjunct 
      evaluated to FALSE.
      It happened because the pushdown condition for table with
      grouping columns lost its constant conjuncts.
      Pushdown conditions are always built by the function make_cond_for_table
      that ignores constant conjuncts. This is apparently not correct when
      constant false conjuncts are present.
      
      
      mysql-test/r/having.result:
        Added A test case for bug #14927.
      mysql-test/t/having.test:
        Added A test case for bug #14927.
      sql/sql_lex.cc:
        Fixed bug #14927.
        Initialized fields for having conditions in  st_select_lex::init_query().
      sql/sql_lex.h:
        Fixed bug #14927.
        Added a field to restore having condititions for execution in SP and PS.
      sql/sql_prepare.cc:
        Fixed bug #14927.
        Added code to restore havinf conditions for execution in SP and PS.
      sql/sql_select.cc:
        Fixed bug #14927.
        Performed evaluation of constant expressions in having clauses.
        If the having condition contains a constant conjunct that is always false
        an empty result set is returned after the optimization phase.
        In this case the corresponding EXPLAIN command now returns 
        "Impossible HAVING" in the last column.
      a400e7fe
  3. 31 Jan, 2006 3 commits
  4. 30 Jan, 2006 4 commits
    • unknown's avatar
      Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-4.1 · 2cb45da8
      unknown authored
      into  mysql.com:/home/alexi/innodb/mysql-4.1-merged
      
      
      2cb45da8
    • unknown's avatar
      Fixed BUG#15653, BUG#16582. · 8eaf6f11
      unknown authored
        Applied innodb-4.1-ss20 snapshot.
      
      
      innobase/btr/btr0sea.c:
        Applied innodb-4.1-ss20 snapshot.
          Account for a race condition when dropping the adaptive
          hash index for a B-tree page (Bug #16582).
          btr_search_drop_page_hash_index(): Retry the operation if a hash
          index with different parameters was built meanwhile. Add
          diagnostics for the case that hash node pointers to the page
          remain. This fix is from Heikki.
          btr_search_info_update_hash(), btr_search_info_update_slow():
          Document the parameter "info" as in/out.
      innobase/fil/fil0fil.c:
        Applied innodb-4.1-ss20 snapshot.
          Keep track on unflushed modifications to file spaces. When
          there are tens of thousnads of file spaces, flushing all files
          in fil_flush_file_spaces() would be very slow (Bug #16582).
          fil_flush_file_spaces(): Only flush unflushed file spaces.
          fil_space_t, fil_system_t: Add a list of unflushed spaces.
      innobase/include/btr0sea.ic:
        Applied innodb-4.1-ss20 snapshot.
          btr_search_info_update_hash(), btr_search_info_update_slow():
          Document the parameter "info" as in/out.
      8eaf6f11
    • unknown's avatar
      Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-4.1 · 43f122c4
      unknown authored
      into  mysql.com:/home/alexi/innodb/mysql-4.1-merged
      
      
      43f122c4
    • unknown's avatar
      Fixed BUG#16387. · cc47eb77
      unknown authored
        Applied innodb-4.1-ss17 snapshot.
        Do not mistake TABLENAME_ibfk_0 for auto-generated id.
      
      
      innobase/dict/dict0dict.c:
        Applied innodb-4.1-ss17 snapshot.
          dict_table_get_highest_foreign_id(): Ignore foreign
          constraint identifiers starting with the pattern
          TABLENAME_ibfk_0 (BUG#16387).
      mysql-test/r/innodb.result:
        Applied innodb-4.1-ss17 snapshot.
          Fixed results for added test case.
      mysql-test/t/innodb.test:
        Applied innodb-4.1-ss17 snapshot.
          Added test case.
      cc47eb77
  5. 27 Jan, 2006 7 commits
  6. 26 Jan, 2006 6 commits
  7. 25 Jan, 2006 4 commits
  8. 24 Jan, 2006 3 commits
  9. 23 Jan, 2006 6 commits
    • unknown's avatar
      Fixed bug #16510: Updating field named like '*name' caused server crash. · e14c9c5d
      unknown authored
      When setup_fields() function finds field named '*' it expands it to the list
      of all table fields. It does so by checking that the first char of
      field_name is '*', but it doesn't checks that the '* is the only char.
      Due to this, when updating table with a field named like '*name', such field
      is wrongly treated as '*' and expanded. This leads to making list of fields
      to update being longer than list of the new values. Later, the fill_record() 
      function crashes by dereferencing null when there is left fields to update,
      but no more values.
      
      Added check in the setup_fields() function which ensures that the field
      expanding will be done only when '*' is the only char in the field name.
      
      
      mysql-test/t/update.test:
        Added test case for bug#16510: Updating field named like '*name' caused server crash
      mysql-test/r/update.result:
        Added test case for bug#16510: Updating field named like '*name' caused server crash
      sql/sql_base.cc:
        Fixed bug #16510: Updating field named like '*name' caused server crash.
        Added check in the setup_fields() function which ensures that the field
        expanding will be done only when '*' is the only char in the field name.
      e14c9c5d
    • unknown's avatar
      Merge gboehn@bk-internal.mysql.com:/home/bk/mysql-4.1 · 736f9c09
      unknown authored
      into  phoenix.(none):/data/mysql-4.1-BK
      
      
      736f9c09
    • unknown's avatar
      Merge svojtovich@bk-internal.mysql.com:/home/bk/mysql-4.1 · a120d6c5
      unknown authored
      into  april.(none):/home/svoj/devel/mysql/BUG16489/mysql-4.1
      
      
      a120d6c5
    • unknown's avatar
      BUG#16489 - utf8 + fulltext leads to corrupt index file. · 0ee28e1a
      unknown authored
      Fixed that UPDATE statement crashes multi-byte charset fulltext index.
      
      
      myisam/ft_update.c:
        Fixed that UPDATE statement crashes multi-byte charset fulltext index.
        While updating, always rewrite multi-byte charset fulltext index.
      mysql-test/r/fulltext2.result:
        Added a testcase for BUG#16489.
      mysql-test/t/fulltext2.test:
        Added a testcase for BUG#16489.
      0ee28e1a
    • unknown's avatar
      Merge neptunus.(none):/home/msvensson/mysql/mysql-4.1 · b0a31047
      unknown authored
      into  neptunus.(none):/home/msvensson/mysql/bug14634/my41-bug14634
      
      
      b0a31047
    • unknown's avatar
      Merge gboehn@bk-internal.mysql.com:/home/bk/mysql-4.1 · c56ae507
      unknown authored
      into  phoenix.(none):/data/mysql-4.1-BK
      
      
      c56ae507
  10. 21 Jan, 2006 3 commits
  11. 19 Jan, 2006 1 commit