1. 20 Nov, 2003 3 commits
  2. 19 Nov, 2003 3 commits
  3. 18 Nov, 2003 3 commits
    • unknown's avatar
      Bug#1826, HANDLER+ALTER TABLE=crash (unfortunately, it cannot be tested in mysql-test suite) · bb055f09
      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)
      bb055f09
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · 74eae76e
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      74eae76e
    • unknown's avatar
      Fix for BUG#1870 · 28d2458c
      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).
      28d2458c
  4. 17 Nov, 2003 5 commits
  5. 16 Nov, 2003 1 commit
  6. 15 Nov, 2003 1 commit
  7. 14 Nov, 2003 1 commit
  8. 12 Nov, 2003 1 commit
  9. 08 Nov, 2003 1 commit
    • unknown's avatar
      fulltext.test, fulltext.result: · 42b2238b
      unknown authored
        one simple trunc* test
      
      
      mysql-test/r/fulltext.result:
        one simple trunc* test
      mysql-test/t/fulltext.test:
        one simple trunc* test
      42b2238b
  10. 05 Nov, 2003 1 commit
  11. 04 Nov, 2003 5 commits
  12. 03 Nov, 2003 6 commits
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-4.0/ · 2458fa03
      unknown authored
      into serg.mylan:/usr/home/serg/Abk/mysql-4.0
      
      2458fa03
    • unknown's avatar
      fixed a bug in boolean fts where a word queue was created based on... · 3d589199
      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
      
      
      3d589199
    • unknown's avatar
      Merge mysql.com:/home/kostja/mysql/mysql-4.0-root · f234dded
      unknown authored
      into mysql.com:/home/kostja/mysql/mysql-4.0-1724
      
      f234dded
    • unknown's avatar
      Merge gbichot@bk-internal.mysql.com:/home/bk/mysql-4.0 · e1eedaa4
      unknown authored
      into mysql.com:/home/mysql_src/mysql-4.0
      
      e1eedaa4
    • unknown's avatar
      When we delete the slave's temp tables from memory, we reset · e88de4b9
      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.
      e88de4b9
    • unknown's avatar
      fix for bug #1724 'WHERE ... IN() optimizer behaviour · 492802d6
      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.
      492802d6
  13. 02 Nov, 2003 3 commits
    • unknown's avatar
      Portability fix · 1f5d2372
      unknown authored
      1f5d2372
    • unknown's avatar
      Merge bk-internal.mysql.com:/home/bk/mysql-4.0 · 3fa4399e
      unknown authored
      into mysql.com:/my/mysql-4.0
      
      3fa4399e
    • unknown's avatar
      Call my_sync() after all data is written to .frm file · 593c3449
      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
      593c3449
  14. 31 Oct, 2003 3 commits
    • unknown's avatar
      4 small items in this: · d1571e50
      unknown authored
      - when we don't have in_addr_t, use uint32.
      - a forgotten initialization of slave_proxy_id in sql/log_event.cc (was not really "forgot", was
      "we needn't init it there", but there was one case where we needed...).
      - made slave_proxy_id always meaningful in THD and Log_event, so we can
      rely more on it (no need to test if it's meaningful). THD::slave_proxy_id
      is equal to THD::thread_id except for the slave SQL thread.
      - clean up the slave's temporary table (i.e. free their memory) when slave
      server shuts down.
      
      
      extra/resolveip.c:
        removed #define as it is simpler to put it in my_net.h
        (because we need the #define elsewhere)
      include/my_net.h:
        When in_addr_t is not defined, use uint32.
      libmysql/libmysql.c:
        using in_addr_t is more generic.
      libmysql/manager.c:
        using in_addr_t is more generic.
      mysql-test/t/rpl_chain_temp_table.test:
        comments
      sql/log_event.cc:
        * Had forgot to initialize slave_proxy_id in the event constructor (char* buf...).
        Initializing is in fact only needed for Create_file_log_event, because
        it uses slave_proxy_id even if it does not write an event to the binlog
        (it uses slave_proxy_id to write it to SQL-LOAD.info).
        * When we write events we now always write slave_proxy_id, which is now always
        meaningful (as thd->slave_proxy_id is now always meaningful, see change in
        sql_class.cc).
      sql/mini_client.cc:
        in_addr_t is more generic.
      sql/slave.cc:
        A RELAY_LOG_INFO method to free the slave's temporary tables from memory
        at slave's server shutdown.
        It is called by end_slave(), which is called by close_connections(),
        which is called when the server terminates
        (close_connections() is just before clean_up(); putting the call in 
        clean_up() was buggy, as active_mi is already deleted by close_connections().
      sql/slave.h:
        new method
      sql/sql_class.cc:
        By default we set THD::slave_proxy_id to THD::thread_id,
        so THD::slave_proxy_id is always meaningful (not 0).
        It's always the same as the thread id except for the slave
        SQL thread.
      d1571e50
    • unknown's avatar
      minor fix in rm · c9966b4e
      unknown authored
      
      libmysqld/Makefile.am:
        minor fix for rm
      c9966b4e
    • unknown's avatar
      thd->query assignment moved out · b0a69f49
      unknown authored
      of lock scope
      
      b0a69f49
  15. 30 Oct, 2003 3 commits