1. 19 Oct, 2005 7 commits
    • unknown's avatar
      Merge mysql.com:/users/lthalmann/bkroot/mysql-5.0 · 75f8dba6
      unknown authored
      into  mysql.com:/users/lthalmann/bk/mysql-5.0-hexdump
      
      
      client/mysqlbinlog.cc:
        Auto merged
      sql/log_event.cc:
        Auto merged
      sql/log_event.h:
        Auto merged
      75f8dba6
    • unknown's avatar
      mysqlbinlog --hexdump patch 4: · 35e61274
      unknown authored
      Rename last_event_info to print_event_info to better reflect the new semantics
      
      
      client/mysqlbinlog.cc:
        Rename last_event_info to print_event_info
      sql/log_event.cc:
        Rename last_event_info to print_event_info
      sql/log_event.h:
        Rename last_event_info to print_event_info
      35e61274
    • unknown's avatar
      A fix and a test case for Bug#13587 "Server crash when SP is created · 9a5dd3b4
      unknown authored
      without database"
      
      
      mysql-test/r/sp-error.result:
        Test results fixed (a test case for Bug#13587)
      mysql-test/t/sp-error.test:
        A test case for Bug#13587 "Server crash when SP is created without 
        database"
      sql/sql_parse.cc:
        - move initialization of lex->sphead->m_db before it's used.
        - cleanup; comment why right now can't be cleaned any more
      9a5dd3b4
    • unknown's avatar
      Merge spetrunia@bk-internal.mysql.com:/home/bk/mysql-5.0 · 2f222cc7
      unknown authored
      into mysql.com:/home/psergey/mysql-5.0-bug12915-merge
      
      2f222cc7
    • unknown's avatar
      Post-merge fixes · 188ce9ec
      unknown authored
      188ce9ec
    • unknown's avatar
      Merge pgalbraith@bk-internal.mysql.com:/home/bk/mysql-5.0 · 68fdec49
      unknown authored
      into  krsna.patg.net:/home/patg/mysql-build/mysql-5.0.test2
      
      68fdec49
    • unknown's avatar
      Changeset: · f415d919
      unknown authored
        Changed option text in mysqldump.c
      mysqldump.c:
        Changed text to read "+00:00" as opposed to "UTC" (per what the code does)
      
      
      client/mysqldump.c:
        Changed text to read "+00:00" as opposed to "UTC" (per what the code does)
      f415d919
  2. 18 Oct, 2005 21 commits
  3. 17 Oct, 2005 12 commits
    • unknown's avatar
      1fa2f356
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 21d0fe01
      unknown authored
      into  mysql.com:/home/emurphy/src/bk-clean/mysql-5.0
      
      21d0fe01
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 057c0f08
      unknown authored
      into  mysql.com:/home/emurphy/src/bk-clean/mysql-5.0
      
      057c0f08
    • unknown's avatar
      Merge pgalbraith@bk-internal.mysql.com:/home/bk/mysql-5.0 · 008e4abf
      unknown authored
      into  krsna.patg.net:/home/patg/mysql-build/mysql-5.0.test1
      
      008e4abf
    • unknown's avatar
      Merge pgalbraith@bk-internal.mysql.com:/home/bk/mysql-5.0 · fff4897f
      unknown authored
      into  krsna.patg.net:/home/patg/mysql-build/mysql-5.0.test1
      
      fff4897f
    • unknown's avatar
      BUG# 13052 Changed text in options to TIMESTAMP · 138f1a25
      unknown authored
      
      client/mysqldump.c:
        BUG# 13052 Changed text in option to TIMESTAMP
      138f1a25
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 17ff2406
      unknown authored
      into  mysql.com:/home/dlenev/src/mysql-5.0-bg12739
      
      
      sql/mysql_priv.h:
        Auto merged
      sql/sql_base.cc:
        Auto merged
      sql/sql_table.cc:
        Auto merged
      17ff2406
    • unknown's avatar
      Fix for bug #12739 "Deadlock in multithreaded environment during creating/ · 1a00e60b
      unknown authored
      droping trigger on InnoDB table".
      
      Deadlock occured in cases when we were trying to create two triggers for
      the same InnoDB table concurrently and both threads were able to reach
      close_cached_table() simultaneously. Bugfix implements new approach to
      table locking and table cache invalidation during creation/dropping
      of trigger.
      
      No testcase is supplied since bug was repeatable only under high concurrency.
      
      
      sql/mysql_priv.h:
        reopen_name_locked_table():
          Changed function signature to make it more robust against erroneous usage.
      sql/sql_base.cc:
        reopen_name_locked_table():
          Changed function signature to make it more robust against erroneous usage.
          Obtaining LOCK_open lock is now resposibility of caller.
          When searching for the table to open we should not prefer connection's current
          database over database which was explicitly specified in TABLE_LIST::db member
          (even if database is not explicitly specified for table in original query
          TABLE_LIST::db will be set properly at parsing stage).
          Fixed behavior of function in cases when error occurs during opening of table.
      sql/sql_table.cc:
        prepare_for_restore()/prepare_for_repair():
          We should not prefer connection's current database over database which was
          specified in TABLE_LIST::db member (even if database is not explicitly
          specified for table in original query TABLE_LIST::db will be set properly
          at parsing stage). Fixed behavior in unlikely case when we are unable
          to open table which we are restoring/reparing at the end of preparation
          stage.
      sql/sql_trigger.cc:
        mysql_create_or_drop_trigger():
          Now instead of opening and locking table, creating trigger, and then trying
          to invalidate all instances of this table in table cache, we obtain name
          lock on table first (thus ensuring that no other thread has this table
          open), open it, create trigger and then close table therefore releasing lock.
          New approach is more in line with other places where change .frm files
          (i.e. change table meta-data).
          With this change we also get rid of deadlock which occured in cases when we
          were trying to create two triggers for the same InnoDB table concurrently
          and both threads were able to reach close_cached_table() simultaneously.
          (Alternative was to forbid to InnoDB downgrade locks for CREATE/DROP
           TRIGGER statements in one way or another but I think that proposed
           solution is better long term).
      1a00e60b
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 9af97324
      unknown authored
      into  mysql.com:/home/emurphy/src/bk-clean/mysql-5.0
      
      9af97324
    • unknown's avatar
      BUG#13900 DATETIME data changes after inserting a new row in a InnoDB table · c5615673
      unknown authored
      Applying patch from Marko.
      All tests pass in pentium-debug-max build on Linux.
      
      
      innobase/include/rem0rec.h:
        BUG#13900 DATETIME data changes after inserting a new row in a InnoDB table
        Applying patch from Marko.
      innobase/include/rem0rec.ic:
        BUG#13900 DATETIME data changes after inserting a new row in a InnoDB table
        Applying patch from Marko.
      innobase/row/row0upd.c:
        BUG#13900 DATETIME data changes after inserting a new row in a InnoDB table
        Applying patch from Marko.
      c5615673
    • unknown's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-5.0 · 162076e4
      unknown authored
      into mysql.com:/Users/kent/mysql/bk/mysql-5.0
      
      162076e4
    • unknown's avatar
      Bug #13377. Small update, code formatting. · df494c54
      unknown authored
      df494c54