1. 25 Nov, 2003 1 commit
    • unknown's avatar
      - Removed COPYING.LIB from all source and binary distributions · 878430e8
      unknown authored
         after it was removed from manual.texi (where it was automatically
         generated from).
      
      
      Docs/Makefile.am:
         - don't create COPYING.LIB anymore (was removed from manual.texi)
      Makefile.am:
         - Removed COPYING.LIB from the source distribution
      scripts/make_binary_distribution.sh:
         - Removed COPYING.LIB from the binary distribution
      scripts/make_win_src_distribution.sh:
         - Removed COPYING.LIB from the windows source distribution
      support-files/mysql.spec.sh:
         - Removed COPYING.LIB from the Server RPM
      878430e8
  2. 24 Nov, 2003 3 commits
    • unknown's avatar
      - Rephrased two option help texts to not start with "use the ..." as this · 4ca9c493
      unknown authored
         confuses RPM's Perl module dependency checking (it adds a bogus
         requirement to "Perl(the)", as "use" is a Perl keyword). (BUG#1931)
      
      
      scripts/mysqlaccess.sh:
         - Rephrased option help text so it does not start with "use" as this 
           confuses RPM's Perl module dependency checking (it adds a bogus
           requirement to "Perl(the)", as "use" is a Perl keyword). (BUG#1931)
      sql-bench/bench-init.pl.sh:
         - Rephrased option help text so it does not start with "use" as this 
           confuses RPM's Perl module dependency checking (it adds a bogus
           requirement to "Perl(the)", as "use" is a Perl keyword). (BUG#1931)
      4ca9c493
    • unknown's avatar
      Merge mysql.com:/space/my/mysql-4.0 · 7427698e
      unknown authored
      into mysql.com:/space/my/mysql-4.0-build
      
      7427698e
    • unknown's avatar
      Fixed Bug#1907, option of type GET_BOOL with arg type OPT_ARG · 5c30ea7c
      unknown authored
      did not call get_one_option().
      
      5c30ea7c
  3. 23 Nov, 2003 1 commit
  4. 21 Nov, 2003 1 commit
  5. 20 Nov, 2003 6 commits
  6. 19 Nov, 2003 3 commits
  7. 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
  8. 17 Nov, 2003 5 commits
  9. 16 Nov, 2003 1 commit
  10. 15 Nov, 2003 1 commit
  11. 14 Nov, 2003 1 commit
  12. 12 Nov, 2003 1 commit
  13. 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
  14. 05 Nov, 2003 1 commit
  15. 04 Nov, 2003 5 commits
  16. 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