1. 24 Aug, 2004 1 commit
    • unknown's avatar
      - make sure to recreate all autoconf/automake-related files after · 4fa7f9c2
      unknown authored
         modifying configure.in for the commercial tarballs
       - added my-innodb-heavy-4G.cnf to the distribution
      
      
      Build-tools/mysql-copyright:
         - make sure to recreate all autoconf/automake-related files after
           modifying configure.in
      support-files/Makefile.am:
         - added my-innodb-heavy-4G.cnf to the distribution
      4fa7f9c2
  2. 23 Aug, 2004 7 commits
  3. 22 Aug, 2004 3 commits
  4. 21 Aug, 2004 1 commit
    • unknown's avatar
      null.test, null.result: · b33b4c27
      unknown authored
        Added test case for bug #4256.
      join_outer.result:
        Fixed bug #4256.
      item_cmpfunc.h:
        Fixed inconsistency of values of used_tables_cache and
        const_item_cache for Item_func_isnull objects.
        This inconsistency caused bug #4256.
      
      
      sql/item_cmpfunc.h:
        Fixed inconsistency of values of used_tables_cache and
        const_item_cache for Item_func_isnull objects.
        This inconsistency caused bug #4256.
      mysql-test/r/join_outer.result:
        Fixed bug #4256.
      mysql-test/r/null.result:
        Added test case for bug #4256.
      mysql-test/t/null.test:
        Added test case for bug #4256.
      b33b4c27
  5. 20 Aug, 2004 3 commits
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · 8003fee8
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      8003fee8
    • unknown's avatar
      Making FLUSH TABLES WITH READ LOCK block COMMITs of existing transactions, · 79b2593f
      unknown authored
      in a deadlock-free manner. This splits locking the global read lock in two steps.
      This fixes a consequence of this bug, known as:
      BUG#4953 'mysqldump --master-data may report incorrect binlog position if using InnoDB'
      And a test.
      
      
      sql/handler.cc:
        making COMMIT wait if FLUSH TABLES WITH READ LOCK happened.
      sql/lock.cc:
        an additional stage so that FLUSH TABLES WITH READ LOCK blocks COMMIT:
        make_global_read_lock_block_commit():
        taking the global read lock is TWO steps (2nd step is optional; without
        it, COMMIT of existing transactions will be allowed):
        lock_global_read_lock() THEN make_global_read_lock_block_commit().
      sql/mysql_priv.h:
        new argument to wait_if_global_read_lock()
      sql/sql_class.h:
        THD::global_read_lock now an uint to reflect the 2 steps of global read lock (does not block COMMIT / does)
      sql/sql_db.cc:
        update for new prototype
      sql/sql_parse.cc:
        implementing the two steps of global read lock so that FLUSH TABLES WITH READ LOCK can block COMMIT without deadlocking with COMMITs.
      79b2593f
    • unknown's avatar
      A fix (bug #5115: Erronious Syntax Error when comment placed inside of "create table") · 80ef38c7
      unknown authored
      
      client/mysql.cc:
        in_comment is now outside the add_line().
      80ef38c7
  6. 19 Aug, 2004 9 commits
  7. 18 Aug, 2004 4 commits
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · bde0645f
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      bde0645f
    • unknown's avatar
      Fix for BUG#4971 "CREATE TABLE ... TYPE=HEAP SELECT ... stops slave (wrong DELETE in binlog)": · 090b38b0
      unknown authored
      replacing the no_log argument of mysql_create_table() by some safer method
      (temporarily setting OPTION_BIN_LOG to 0) which guarantees that even the automatic
      DELETE FROM heap_table does not get into the binlog when a not-yet-existing HEAP table
      is opened by mysql_create_table().
      
      
      mysql-test/r/rpl_heap.result:
        result update
      mysql-test/t/rpl_heap.test:
        testing a bug
      sql/log.cc:
        new class Disable_binlog used to temporarily disable binlogging for one thread.
      sql/mysql_priv.h:
        removing argument no_log from mysql_create_table(); no_log was perfect as some
        binlogging could still be done by open_unireg_entry() for a HEAP table.
      sql/sql_class.h:
        new class Disable_binlog used to temporarily disable binlogging for one thread.
      sql/sql_parse.cc:
        removing no_log
      sql/sql_table.cc:
        removing no_log from mysql_create_table(); instead using new class Disable_binlog.
        Disabling binlogging in some cases, where the binlogging is done later by some other code
        (case of CREATE SELECT and ALTER).
      090b38b0
    • unknown's avatar
      Bug 4937: different date -> string conversion when using · 8c83ab40
      unknown authored
      SELECT ... UNION and INSERT ... SELECT ... UNION
      
      8c83ab40
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-4.0/ · e20b1a57
      unknown authored
      into serg.mylan:/usr/home/serg/Abk/mysql-4.0
      
      e20b1a57
  8. 17 Aug, 2004 6 commits
    • unknown's avatar
      srv0start.c, ut0mem.c, ut0dbg.c, ut0dbg.h, srv0start.h: · 63fc705a
      unknown authored
        Changes for NetWare to exit the InnoDB gracefully instead of crashing the server (patch by PRam@novell.com, polished a little by Heikki Tuuri)
      mysqld.cc, ha_innodb.cc:
        Changes for NetWare to exit the InnoDB gracefully instead of crashing the server (patch by PRam@novell.com, polished a little by Heikki Tuuri) 
      
      
      sql/ha_innodb.cc:
        Changes for NetWare to exit the InnoDB gracefully instead of crashing the server (patch by PRam@novell.com, polished a little by Heikki Tuuri)
      sql/mysqld.cc:
        Changes for NetWare to exit the InnoDB gracefully instead of crashing the server (patch by PRam@novell.com, polished a little by Heikki Tuuri)
      innobase/include/srv0start.h:
        Changes for NetWare to exit the InnoDB gracefully instead of crashing the server (patch by PRam@novell.com, polished a little by Heikki Tuuri)
      innobase/include/ut0dbg.h:
        Changes for NetWare to exit the InnoDB gracefully instead of crashing the server (patch by PRam@novell.com, polished a little by Heikki Tuuri)
      innobase/ut/ut0dbg.c:
        Changes for NetWare to exit the InnoDB gracefully instead of crashing the server (patch by PRam@novell.com, polished a little by Heikki Tuuri)
      innobase/ut/ut0mem.c:
        Changes for NetWare to exit the InnoDB gracefully instead of crashing the server (patch by PRam@novell.com, polished a little by Heikki Tuuri)
      innobase/srv/srv0start.c:
        Changes for NetWare to exit the InnoDB gracefully instead of crashing the server (patch by PRam@novell.com, polished a little by Heikki Tuuri)
      63fc705a
    • unknown's avatar
      use my_vsnprintf() just in case · 589f9a26
      unknown authored
      bug#4925
      
      589f9a26
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · 953e6859
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      953e6859
    • unknown's avatar
      Fix for BUG#5073 "--disable-local-infile has no effect if client reads it with MYSQL_READ_DEFAULT": · 9859027c
      unknown authored
      that was a forgotten '~' probably.
      
      
      libmysql/libmysql.c:
        When we read "disable-local-infile" from the option file specified by mysql_options(MYSQL_READ_DEFAULT_FILE),
        we must take CLIENT_LOCAL_FILES down (it was probably a forgotten '~').
      9859027c
    • unknown's avatar
      Merge heikki@build.mysql.com:/home/bk/mysql-4.0 · f4b148ca
      unknown authored
      into hundin.mysql.fi:/home/heikki/mysql-4.0
      
      f4b148ca
    • unknown's avatar
      A fix (bug #5055: SQL_SELECT_LIMIT=0 crashes command line client): · f9525e9d
      unknown authored
      mysql outwits itself.
      
      f9525e9d
  9. 16 Aug, 2004 2 commits
  10. 14 Aug, 2004 2 commits
  11. 13 Aug, 2004 2 commits
    • unknown's avatar
      row0mysql.c: · 09182527
      unknown authored
        Fix bug: if we RENAME a table, InnoDB forgot to load the foreign key constraints that reference the new table name, and forgot to check that they are compatible with the table
      
      
      innobase/row/row0mysql.c:
        Fix bug: if we RENAME a table, InnoDB forgot to load the foreign key constraints that reference the new table name, and forgot to check that they are compatible with the table
      09182527
    • unknown's avatar
      - manual merge · c269ff4e
      unknown authored
      c269ff4e