1. 09 Feb, 2004 1 commit
  2. 08 Feb, 2004 2 commits
    • unknown's avatar
      Many files: · cd361b41
      unknown authored
        Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication
      sync0sync.c:
        UNIV_SYNC_DEBUG caused assertion in the creation of the doublewrite buffer, if we do not allow thousands of latches per thread
      
      
      innobase/dict/dict0crea.c:
        Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication
      innobase/dict/dict0dict.c:
        Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication
      innobase/include/dict0crea.h:
        Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication
      innobase/include/dict0dict.h:
        Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication
      innobase/include/ut0mem.h:
        Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication
      innobase/row/row0mysql.c:
        Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication
      innobase/sync/sync0sync.c:
        UNIV_SYNC_DEBUG caused assertion in the creation of the doublewrite buffer, if we do not allow thousands of latches per thread
      innobase/ut/ut0mem.c:
        Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication
      cd361b41
    • unknown's avatar
      ha_innodb.cc: · b0076aad
      unknown authored
        If AUTOCOMMIT=1, then we do not need to make a plain SELECT set shared locks even on the SERIALIZABLE isolation level, because we know the transaction is read-only: a read-only transaction can always be performed on the REPEATABLE READ level, and that does not endanger the serializability
      
      
      sql/ha_innodb.cc:
        If AUTOCOMMIT=1, then we do not need to make a plain SELECT set shared locks even on the SERIALIZABLE isolation level, because we know the transaction is read-only: a read-only transaction can always be performed on the REPEATABLE READ level, and that does not endanger the serializability
      b0076aad
  3. 06 Feb, 2004 6 commits
    • unknown's avatar
      Delete: COPYING.LIB · 496cbfe8
      unknown authored
      496cbfe8
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.0 · 629dda9c
      unknown authored
      into mysql.com:/home/kostja/mysql/mysql-4.0-merge
      
      
      629dda9c
    • unknown's avatar
      fixed bug #1378 "mysqlbinlog for remote host is broken" · 7db76e5a
      unknown authored
      
      client/mysqlbinlog.cc:
        fixed bug #1378 "mysqlbinlog for remote host is broken"
        by using shared part of code for local and remote variant 
        (function process_event)
      mysql-test/r/mysqlbinlog.result:
        fixed results for remote variant 
        (they are the same as for local now)
      mysql-test/t/mysqlbinlog.test:
        discarded note 'V. Vagin should ...' 
        because V.Vagin done
      sql/log_event.cc:
        added special local_fname flag to Load_log_event for 
        using in Load_log_event::check_fname_outside_temp_buf 
        instead of ugly condition
      sql/log_event.h:
        added special local_fname flag to Load_log_event for 
        using in Load_log_event::check_fname_outside_temp_buf 
        instead of ugly condition
      7db76e5a
    • unknown's avatar
      3.23 -> 4.0 merge: after merge fixes · 854076da
      unknown authored
      854076da
    • unknown's avatar
      merge 3.23 -> 4.0, 2003/02/06 · 5db2d195
      unknown authored
      
      BitKeeper/etc/ignore:
        auto-union
      BitKeeper/etc/logging_ok:
        auto-union
      mysql-test/r/func_math.result:
        Auto merged
      mysql-test/t/func_math.test:
        Auto merged
      sql/item_func.cc:
        Auto merged
      5db2d195
    • unknown's avatar
      Fix for bug #2628 "ALTER TABLE destroys table and reports success" · b5819094
      unknown authored
      
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      mysql-test/r/alter_table.result:
        Fix for bug #2628: test result fixed
      mysql-test/t/alter_table.test:
        Fix for bug #2628: test case added
      sql/sql_table.cc:
        Fix for bug #2628:
        We need to take into account database name when checking if source and 
        destination table names are equal.
        Note, that after merge to 4.0 we also need to check for 
        lower_case_table_names.
      b5819094
  4. 05 Feb, 2004 8 commits
    • unknown's avatar
      - updated config.guess, config.sub and ltmain.sh with versions from libtool · 15b89bfc
      unknown authored
         1.5 to fix BUG#202 (update config.guess & co for MIPS architecture)
      
      
      config.guess:
         - upplied diffs from libtool 1.5
      config.sub:
         - upplied diffs from libtool 1.5
      ltmain.sh:
         - upplied diffs from libtool 1.5
      15b89bfc
    • unknown's avatar
      Merge lgrimmer@build.mysql.com:/home/bk/mysql-4.0 · 00bcf494
      unknown authored
      into mysql.com:/space/my/mysql-4.0
      
      
      00bcf494
    • unknown's avatar
      - renamed mysql-test/t/init_file.sql to mysql-test/std_data/init_file.dat · 62a4ae07
      unknown authored
         so it gets picked up by "make dist" and updated init_file test accordingly.
      
      
      mysql-test/std_data/init_file.dat:
        Rename: mysql-test/t/init_file.sql -> mysql-test/std_data/init_file.dat
      mysql-test/t/init_file-master.opt:
         - moved init file to std_data
      mysql-test/t/init_file.test:
         - updated info
      62a4ae07
    • unknown's avatar
      include atomic.h in extern "C" mode · b40d4e12
      unknown authored
      b40d4e12
    • unknown's avatar
      Merge vvagin@bk-internal.mysql.com:/home/bk/mysql-4.0 · b8004902
      unknown authored
      into eagle.mysql.r18.ru:/home/vva/work/BUG_2526/mysql-4.0
      
      
      b8004902
    • unknown's avatar
      Merge eagle.mysql.r18.ru:/home/vva/work/mysql.orig/clear/mysql-4.0 · f79ff0f9
      unknown authored
      into eagle.mysql.r18.ru:/home/vva/work/BUG_2526/mysql-4.0
      
      
      sql/sql_class.cc:
        Auto merged
      f79ff0f9
    • unknown's avatar
      code cleanup · b911f9b0
      unknown authored
      b911f9b0
    • unknown's avatar
      Added testing of pthread_key_delete (to fix compile problem on SCO) (Bug #2461) · d295f07c
      unknown authored
      DROP DATABASE now assumes RAID directories are in hex. (Bug #2627)
      Don't increment 'select_full_range' and similar statistics for EXPLAIN queries. (Bug #2506)
      Test in configure if pthread_key_delete() exists (to fix compile problem on SCO) (Bug #2461)
      
      
      BUILD/compile-pentium-max:
        Added --with-raid
      configure.in:
        Added testing of pthread_key_delete (to fix compile problem on SCO)  (Bug #2461)
      include/my_pthread.h:
        Added testing of pthread_key_delete (to fix compile problem on SCO)  (Bug #2461)
      innobase/include/data0data.ic:
        Added missing newline
      mysql-test/r/raid.result:
        Test of DROP DATABASE with RAID directories in hex
      mysql-test/t/raid.test:
        Test of DROP DATABASE with RAID directories in hex
      sql/sql_db.cc:
        DROP DATABASE could not drop databases with RAID tables that had
        more than 9 RAID_CHUNKS because DROP DATABASE assumed raid tables where in decimal while the RAID CREATE code assumed directories was in hex.(Bug #2627)
      sql/sql_select.cc:
        Don't increment 'select_full_range' and similar statistics for EXPLAIN queries. (Bug #2506)
      sql/sql_udf.cc:
        mysqld crashed if mysql.func table didn't exists (Bug #2577)
      d295f07c
  5. 04 Feb, 2004 17 commits
  6. 03 Feb, 2004 6 commits