1. 19 Oct, 2005 8 commits
  2. 18 Oct, 2005 21 commits
  3. 17 Oct, 2005 11 commits
    • unknown's avatar
      0122ca60
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 49242dda
      unknown authored
      into  mysql.com:/home/emurphy/src/bk-clean/mysql-5.0
      
      
      49242dda
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 4ba953f5
      unknown authored
      into  mysql.com:/home/emurphy/src/bk-clean/mysql-5.0
      
      
      4ba953f5
    • unknown's avatar
      Merge pgalbraith@bk-internal.mysql.com:/home/bk/mysql-5.0 · 83c1adb4
      unknown authored
      into  krsna.patg.net:/home/patg/mysql-build/mysql-5.0.test1
      
      
      83c1adb4
    • unknown's avatar
      Merge pgalbraith@bk-internal.mysql.com:/home/bk/mysql-5.0 · cf584ced
      unknown authored
      into  krsna.patg.net:/home/patg/mysql-build/mysql-5.0.test1
      
      
      cf584ced
    • unknown's avatar
      BUG# 13052 Changed text in options to TIMESTAMP · 98b4390f
      unknown authored
      
      client/mysqldump.c:
        BUG# 13052 Changed text in option to TIMESTAMP
      98b4390f
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 5727309d
      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
      5727309d
    • unknown's avatar
      Fix for bug #12739 "Deadlock in multithreaded environment during creating/ · dd02b98d
      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).
      dd02b98d
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-5.0 · 22af54a9
      unknown authored
      into  mysql.com:/home/emurphy/src/bk-clean/mysql-5.0
      
      
      22af54a9
    • unknown's avatar
      BUG#13900 DATETIME data changes after inserting a new row in a InnoDB table · 955798d2
      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.
      955798d2
    • unknown's avatar
      Merge kboortz@bk-internal.mysql.com:/home/bk/mysql-5.0 · dddc50f2
      unknown authored
      into mysql.com:/Users/kent/mysql/bk/mysql-5.0
      
      
      dddc50f2