- 08 Dec, 2006 1 commit
-
-
unknown authored
- test* targets are identical (as much as possible) to 5.0 & 5.1 versions - use @PERL@ ./mysql-test-run.pl, instead of depending on /usr/bin/perl location - PHONY: target includes all test targets Makefile.am: - test* targets are identical (as much as possible) to 5.0 & 5.1 versions - use @PERL@ ./mysql-test-run.pl, instead of depending on /usr/bin/perl location - PHONY: target includes all test targets
-
- 05 Dec, 2006 6 commits
-
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
-
unknown authored
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
into rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-4.1-maint
-
unknown authored
- Comment Cleanup. sql/sql_class.cc: Removed misleading comment.
-
unknown authored
mysql-test/mysql-test-run.pl: delete $default_vardir if the 4.1 vardir trick is to be used to re-enable more than one test run in sequence
-
- 04 Dec, 2006 4 commits
-
-
unknown authored
into rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-4.1-maint sql/sql_class.h: Auto merged
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint Makefile.am: Auto merged client/mysqltest.c: Auto merged mysql-test/lib/mtr_process.pl: Auto merged mysql-test/mysql-test-run.pl: Auto merged sql/mysqld.cc: Auto merged
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
-
unknown authored
- Add CR_CONN_HOST_ERROR to list of errorcode that trigger another connection attempt in mysqltest client/mysqltest.c: Add CR_CONN_HOST_ERROR to errorcodes that trigger a reconnect
-
- 01 Dec, 2006 2 commits
- 30 Nov, 2006 4 commits
-
-
unknown authored
mysql-test/lib/mtr_process.pl: print extra message _once_ every 60 seconds
-
unknown authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-4.1-opt
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
-
- 29 Nov, 2006 9 commits
-
-
unknown authored
into bodhi.local:/opt/local/work/mysql-4.1-runtime
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
-
unknown authored
Remove soft links before creating source TAR, to avoid file copies (bug#11865) Makefile.am: Remove soft links before creating source TAR, to avoid file copies (bug#11865)
-
unknown authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-4.1-opt
-
unknown authored
into dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-4.1-opt
-
unknown authored
into kahlann.erinye.com:/home/df/mysql/build/mysql-4.1-build-work
-
unknown authored
mysql-test/mysql-test-run.pl: remove dependency on Data::Dumper, it's not used anywhere
-
unknown authored
the problem is that client tools are compiled with UNDEF_THREADS_HACK flag, and my thread-related additions to the mysqltest.c can't be compiled. Easy solution is to disable these in not-embedded case completely. client/mysqltest.c: it's used in embedded server only
-
- 28 Nov, 2006 14 commits
-
-
unknown authored
into bodhi.local:/opt/local/work/mysql-4.1-runtime libmysql/libmysql.c: Auto merged libmysqld/lib_sql.cc: Auto merged sql/item_sum.cc: Auto merged
-
unknown authored
This error is displayed anytime the SELECT statement needs a temp table to return correct results because the object (select_dumpvar) that represents variables named in the INTO clause stored the results before the temp table was considered. The problem was fixed by creating the necessary Item_func_set_user_var objects once the correct data is ready. mysql-test/r/distinct.result: Bug#20836 Selecting into variables results in wrong results being returned - Added results mysql-test/t/distinct.test: Bug#20836 Selecting into variables results in wrong results being returned - Added various Selects that use the INTO statement and a temp table. - Added Select Into Outfile variant tests also. sql/sql_class.cc: Bug#20836 Selecting into variables results in wrong results being returned - The select_dumpvar variable created a Item_func_set_user_var too early and once set, it was not possible to change. The Item_func_set_user_var is now created once the final results are available. sql/sql_class.h: Bug#20836 Selecting into variables results in wrong results being returned - Removed unnecessary object members.
-
unknown authored
where we know how to creat the vardir Remove unused variable
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
- Avoid use of mtr_run when executing "mysqld --verbose --help" to find version and supported features mysql-test/mysql-test-run.pl: Don't use mtr_run when executing "mysqld --verbose --help" to find version and supported features.
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint client/mysqltest.c: Auto merged Makefile.am: Manual merge mysql-test/mysql-test-run.pl: Manual merge
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
in all cuurently known log files
-
unknown authored
After that it will by default use log tables. That setting can be overruled by adding a -master.opt file like mysql_client_test has.
-
unknown authored
ALTER TABLE DISABLE KEYS doesn't work when modifying the table ENABLE|DISABLE KEYS combined with another ALTER TABLE option, different than RENAME TO did nothing. Also, if the table had disabled keys and was ALTER-ed then the end table was with enabled keys. Fixed by checking whether the table had disabled keys and enabling them in the copied table. myisam/mi_open.c: Extend mi_indexes_are_disabled to implement return value 2 - Non-unique indexes are disabled mysql-test/r/alter_table.result: update result mysql-test/t/alter_table.test: update test sql/sql_table.cc: When ENABLE|DISABLE index is combined with another option different than RENAME TO, we should ENABLE|DISABLE the keys of the modified table. Also when modifying we should preserve the previous state of the indices. (This problem exists in 5.0 and 5.1 but since the codebase has diverged, this fix won't automerge, but the fix will be quite similar).
-
unknown authored
If using \$(srcdir)/mysql.info in action, use same in rule. Docs/Makefile.am: If using \$(srcdir)/mysql.info in action, use same in rule.
-
unknown authored
-