1. 04 Dec, 2003 1 commit
  2. 24 Nov, 2003 1 commit
  3. 23 Nov, 2003 1 commit
  4. 20 Nov, 2003 6 commits
  5. 19 Nov, 2003 3 commits
  6. 18 Nov, 2003 3 commits
    • unknown's avatar
      Bug#1826, HANDLER+ALTER TABLE=crash (unfortunately, it cannot be tested in mysql-test suite) · a36145a8
      unknown authored
      more user variable tests
      
      
      mysql-test/r/user_var.result:
        more user variable tests (just to have this behaviour written down somewhere)
      mysql-test/t/user_var.test:
        more user variable tests (just to have this behaviour written down somewhere)
      sql/sql_handler.cc:
        Bug#1826, HANDLER+ALTER TABLE=crash
        (unfortunately, it cannot be tested in mysql-test suite)
      a36145a8
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · 40c951a0
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      
      40c951a0
    • unknown's avatar
      Fix for BUG#1870 · 80649ee8
      unknown authored
          "CHANGE MASTER makes SQL thread restart from coordinates of I/O thread".
          So, in CHANGE MASTER:
          when it seems reasonable that the user did not want to discontinue
          its replication (i.e. when he is not specifying host or port or master_log_file
          or master_log_pos; this will be documented), set the coordinates of the
          I/O thread to those of the SQL thread. This way, the SQL thread will see
          no discontinuity in the relay log (i.e. will skip no events), because
          the I/O thread will fill the brand new relay log with the events which
          are just after the position where the SQL thread had stopped
          (before CHANGE MASTER was issued).
          And a new test for this bug.
      
      
      mysql-test/r/rpl_loaddata.result:
        Now, after CHANGE MASTER the coordinates of the I/O thread are the last ones of the SQL thread, so result update.
      sql/sql_repl.cc:
        Fix for BUG#1870
        "CHANGE MASTER makes SQL thread restart from coordinates of I/O thread".
        So, in CHANGE MASTER:
        when it seems reasonable that the user did not want to discontinue
        its replication (i.e. when he is not specifying host or port or master_log_file
        or master_log_pos; this will be documented), set the coordinates of the
        I/O thread to those of the SQL thread. This way, the SQL thread will see
        no discontinuity in the relay log (i.e. will skip no events), because
        the I/O thread will fill the brand new relay log with the events which
        are just after the position where the SQL thread had stopped
        (before CHANGE MASTER was issued).
      80649ee8
  7. 17 Nov, 2003 5 commits
  8. 16 Nov, 2003 1 commit
  9. 15 Nov, 2003 1 commit
  10. 14 Nov, 2003 1 commit
  11. 12 Nov, 2003 1 commit
  12. 08 Nov, 2003 1 commit
    • unknown's avatar
      fulltext.test, fulltext.result: · 20da41c5
      unknown authored
        one simple trunc* test
      
      
      mysql-test/r/fulltext.result:
        one simple trunc* test
      mysql-test/t/fulltext.test:
        one simple trunc* test
      20da41c5
  13. 05 Nov, 2003 1 commit
  14. 04 Nov, 2003 5 commits
  15. 03 Nov, 2003 6 commits
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-4.0/ · 56ebe77b
      unknown authored
      into serg.mylan:/usr/home/serg/Abk/mysql-4.0
      
      
      56ebe77b
    • unknown's avatar
      fixed a bug in boolean fts where a word queue was created based on... · 91b22c5a
      unknown authored
      fixed a bug in boolean fts where a word queue was created based on min_word_len, while with trunc* operator one could get shorter words
      
      
      
      91b22c5a
    • unknown's avatar
      Merge mysql.com:/home/kostja/mysql/mysql-4.0-root · bc296f94
      unknown authored
      into mysql.com:/home/kostja/mysql/mysql-4.0-1724
      
      
      bc296f94
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · fdd0e707
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      
      fdd0e707
    • unknown's avatar
      When we delete the slave's temp tables from memory, we reset · 5ec3a671
      unknown authored
      rli->save_temporary_tables and slave_open_temp_tables
      (in old 4.0 you could make "SHOW STATUS LIKE 'slave_open_temp_tables'" grow
      indefinitely by doing RESET SLAVE and replicating always the same CREATE
      TEMPORARY TABLE).
      It's critical to reset save_temporary_tables to 0 (otherwise you may later
      read memory which has been freed) so this changeset should go into 4.1.
      
      
      mysql-test/r/rpl_reset_slave.result:
        result update
      mysql-test/t/rpl_reset_slave.test:
        test for RESET SLAVE and creating twice the same temp table in the slave.
      sql/slave.cc:
        when we delete the slave's temp tables (when slave server shuts down and when
        RESET SLAVE), we reset 2 variables: rli->save_temporary_tables & slave_open_temp_tables.
      5ec3a671
    • unknown's avatar
      fix for bug #1724 'WHERE ... IN() optimizer behaviour · 22bc137c
      unknown authored
      has changed since 4.0.14'
      We need to calculate cost of RANGE
      scan if it is present instead of cost of 
      FULL scan.
      
      
      mysql-test/r/order_by.result:
        more accurate row estimation
        for RANGE scan
      mysql-test/r/range.result:
        added test case for bug #1724
        'WHERE ... IN() optimizer behaviour has changed since 4.0.14'
      mysql-test/r/select.result:
        please ignore
      mysql-test/t/range.test:
        added test case for bug #1724
        'WHERE ... IN() optimizer behaviour has changed since 4.0.14'
      sql/sql_select.cc:
        fix for bug #1724 'WHERE ... IN() optimizer behaviour 
        has changed since 4.0.14'
        We need to calculate cost of RANGE
        scan instead of cost of FULL scan
        if RANGE is present
        Few comments cleaned up.
      22bc137c
  16. 02 Nov, 2003 3 commits
    • unknown's avatar
      Portability fix · 15cc0ad2
      unknown authored
      15cc0ad2
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.0 · 7960f2c4
      unknown authored
      into mysql.com:/my/mysql-4.0
      
      
      7960f2c4
    • unknown's avatar
      Call my_sync() after all data is written to .frm file · c97a38c4
      unknown authored
      Added my_sync() to mysys which will do fsync/fdatasync/_commit() on a file.
      
      
      VC++Files/mysys/mysys.dsp:
        Added my_sync.c
      configure.in:
        Added testing of fsync and fdatasync
      include/my_sys.h:
        Added my_sync()
      include/mysys_err.h:
        Added my_sync()
      isam/extra.c:
        Added my_sync()
      myisam/mi_extra.c:
        Added my_sync()
      myisam/mi_locking.c:
        Added my_sync()
      mysql-test/mysql-test-run.sh:
        Added option --valgrind-all
      mysys/Makefile.am:
        Added my_sync.c
      mysys/errors.c:
        Added my_sync()
      mysys/my_symlink.c:
        Removed compiler warning
      mysys/thr_alarm.c:
        Fix for link error on windows
      sql/unireg.cc:
        Call my_sync() after all data is written to .frm file
      BitKeeper/etc/logging_ok:
        Logging to logging@openlogging.org accepted
      c97a38c4