- 25 Nov, 2003 1 commit
-
-
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
-
- 24 Nov, 2003 3 commits
-
-
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)
-
unknown authored
into mysql.com:/space/my/mysql-4.0-build
-
unknown authored
did not call get_one_option().
-
- 23 Nov, 2003 1 commit
-
-
unknown authored
mysql-test/r/rpl_change_master.result: Updated results
-
- 21 Nov, 2003 1 commit
-
-
unknown authored
as it is not really required. (BUG 1610) Thanks to Scott Harrison for the suggestion. support-files/mysql.spec.sh: - removed dependency on MySQL-client from the MySQL-devel subpackage as it is not really required. (BUG 1610)
-
- 20 Nov, 2003 6 commits
-
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
unknown authored
-
unknown authored
The right way to fix this is to change the Field::store(longlong) method to be Field::store(longlong, bool unsigned_flag), but this is better to do in 4.1 than in 4.0 mysql-test/r/bigint.result: New tests to show how the last bigint patch broke MySQL mysql-test/t/bigint.test: New tests to show how the last bigint patch broke MySQL sql/item.cc: Revert patch for bigint handling in double context as it broke normal bigint handling sql/item.h: Revert patch for bigint handling in double context as it broke normal bigint handling
-
unknown authored
mysql-test/r/fulltext.result: SCCS merged mysql-test/t/fulltext.test: SCCS merged
-
unknown authored
-
unknown authored
-
- 19 Nov, 2003 3 commits
-
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
unknown authored
minor fixups: more verbose on "no memory" errors - report requested size, avoid flushing rec buffer to a file that is closed and deleted already (on got_error=1)
-
unknown authored
setting LIBS to include @openss_libs@ (BUG#1652)
-
- 18 Nov, 2003 3 commits
-
-
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)
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
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).
-
- 17 Nov, 2003 5 commits
-
-
unknown authored
BUILD/compile-pentium-gcov: Use local file mysys/thr_alarm.c: Get comment from 3.23 sql/mini_client.cc: Get comment from 3.23
-
unknown authored
-
unknown authored
myisam/mi_test2.c: Moved test so that resize_key_cache() is always tested mysys/mf_keycache.c: Fixed comment
-
unknown authored
into mashka.mysql.fi:/home/my/mysql-3.23
-
unknown authored
mysys/thr_alarm.c: Safety fix for alarms on windows sql/mini_client.cc: Added comments
-
- 16 Nov, 2003 1 commit
-
-
unknown authored
BitKeeper/etc/ignore: Added sql/udf_example.so to the ignore list
-
- 15 Nov, 2003 1 commit
-
-
unknown authored
scripts/Makefile.am: added processing of @WRAPLIBS@ in scripts scripts/mysql_config.sh: added @WRAPLIBS@ to embedded_libs option line
-
- 14 Nov, 2003 1 commit
-
-
unknown authored
-
- 12 Nov, 2003 1 commit
-
-
unknown authored
-
- 08 Nov, 2003 1 commit
-
-
unknown authored
one simple trunc* test mysql-test/r/fulltext.result: one simple trunc* test mysql-test/t/fulltext.test: one simple trunc* test
-
- 05 Nov, 2003 1 commit
-
-
unknown authored
Thanks to Daniel Convissor BitKeeper/etc/logging_ok: Logging to logging@openlogging.org accepted
-
- 04 Nov, 2003 5 commits
-
-
unknown authored
into mysql.com:/home/walrus/bk/40
-
unknown authored
Stop line wraping for compiler warnings. It needs for warnings statistic in code coverage BUILD/compile-pentium-gcov: Stop line wraping for compiler warnings. It needs for warnings statistic in code coverage
-
unknown authored
Stop the line wrapping for warnings. it needs for warnings statistic in code coverage BUILD/compile-pentium-gcov: Stop the line wrapping for warnings. it needs for warnings statistic in code coverage
-
unknown authored
into mysql.com:/home/kostja/mysql/mysql-4.0-root
-
unknown authored
mysql-test/t/range.test: Word Police memo is abided
-
- 03 Nov, 2003 6 commits
-
-
unknown authored
into serg.mylan:/usr/home/serg/Abk/mysql-4.0
-
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
-
unknown authored
into mysql.com:/home/kostja/mysql/mysql-4.0-1724
-
unknown authored
into mysql.com:/home/mysql_src/mysql-4.0
-
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.
-
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.
-