1. 23 Feb, 2006 1 commit
    • unknown's avatar
      Remove 'delayed' to make the test deterministic (already · ea9ea952
      unknown authored
      fixed in 5.0).
      A post-review fix (Bug#13134)
      
      
      mysql-test/r/heap.result:
        Remove 'delayed' to make the test deterministic.
      mysql-test/r/ps.result:
        Remove an unneeded drop table (test case for Bug#13134)
      mysql-test/t/heap.test:
        Remove 'delayed' to make the test deterministic.
      mysql-test/t/ps.test:
        A post-review fix (Bug#13134)
      ea9ea952
  2. 21 Feb, 2006 1 commit
    • unknown's avatar
      A fix and a test case for Bug#13134 "Length of VARCHAR() utf8 · 9cf3f255
      unknown authored
      column is increasing when table is recreated with PS/SP":
      make use of create_field::char_length more consistent in the code.
      Reinit create_field::length from create_field::char_length
      for every execution of a prepared statement (actually fixes the 
      bug).
      
      
      mysql-test/r/ps.result:
        Test results fixed (Bug#13134)
      mysql-test/t/ps.test:
        A test case for Bug#13134 "Length of VARCHAR() utf8 column is 
        increasing when table is recreated with PS/SP"
      sql/field.cc:
        Move initialization of create_field::char_length to the constructor
        of create_field.
      sql/field.h:
        Rename chars_length to char_length (to be consistent with
        how this term is used throughout the rest of the code).
      sql/sql_parse.cc:
        Initialize char_length in add_field_to_list. This function
        effectively works as another create_field constructor.
      sql/sql_table.cc:
        Reinit length from char_length for every field in 
        mysql_prepare_table. This is not needed if we're executing
        a statement for the first time, however, at subsequent executions
        length contains the number of bytes, not characters (as it's expected 
        to).
      9cf3f255
  3. 01 Feb, 2006 1 commit
    • 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
  4. 31 Jan, 2006 3 commits
  5. 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
  6. 27 Jan, 2006 7 commits
  7. 26 Jan, 2006 6 commits
  8. 25 Jan, 2006 4 commits
  9. 24 Jan, 2006 3 commits
  10. 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
  11. 21 Jan, 2006 3 commits
  12. 19 Jan, 2006 1 commit