- 28 Mar, 2006 6 commits
-
-
unknown authored
-
unknown authored
into rurik.mysql.com:/home/igor/mysql-5.0
-
unknown authored
An invalid assertion in Item_direct_view_ref::eq caused an assertion abort in the debug version. mysql-test/r/view.result: Added a test case for bug #18386. mysql-test/t/view.test: Added a test case for bug #18386. sql/item.cc: Fixed bug #18386. An invalid assertion in Item_direct_view_ref::eq caused an assertion abort in the debug version. Changed the assertion.
-
unknown authored
into zim.(none):/home/ian/workspace/mysql-5.0
-
unknown authored
BitKeeper/etc/ignore: Added mysql-test/r/udf.log to the ignore list mysql-test/t/disabled.def: Disable the udf test, per bug #18564. Permission by Brian
-
unknown authored
BitKeeper/etc/ignore: Added mysql-test/r/bdb.log mysql-test/r/im_client_port.log to the ignore list client/mysql.cc: If --socket is not set, provides --protocol=TCP when --port= is specified (and --protocol= is not specified.)
-
- 27 Mar, 2006 20 commits
-
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
unknown authored
Remove Solaris -xc99=none C option as C++ compiler can't handle it scripts/mysql_config.sh: Remove Solaris -xc99=none C option as C++ compiler can't handle it
-
unknown authored
in older version. The problem is that TRN-files created in "old" versions contain junk in trigger_table field, which is not acceptable in "new" versions. sql/parse_file.cc: 1. Made parse_escaped_string() available globally; 2. Polishing: fixing the comments. sql/parse_file.h: Made parse_escaped_string() available globally. sql/sql_trigger.cc: 1. Polishing 2. Removed declaration of global handle_old_incorrect_sql_modes() since it is not used anymore. 3. Added a hook to support invalid "trigger_table" field in TRN-file from old versions.
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0-new
-
unknown authored
We are not to control what malloc package others are to use, remove -lmtmalloc from --libs(_r), bug#18322 scripts/mysql_config.sh: We are not to control what malloc package others are to use, remove -lmtmalloc from --libs(_r), bug#18322
-
unknown authored
into mysql.com:/home/my/mysql-5.0
-
unknown authored
into mysql.com:/space/pekka/ndb/version/my50
-
unknown authored
ndb/src/ndbapi/NdbDictionaryImpl.cpp: check parseTableInfo return value to avoid coredump seen on solaris when charsets missing on client host
-
unknown authored
into mysql.com:/home/my/mysql-5.0
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
unknown authored
Reproduced in 5.0.16-nt. Tested to work in 5.0.20 mysql-test/r/group_min_max.result: Test case for BUG#15102 : select distinct returns empty result, select count distinct > 0 (correct) Reproduced in 5.0.16-nt. Tested to be fixed in 5.0.20 mysql-test/t/group_min_max.test: Test case for BUG#15102 : select distinct returns empty result, select count distinct > 0 (correct) Reproduced in 5.0.16-nt. Tested to be fixed in 5.0.20
-
unknown authored
into mysql.com:/home/my/mysql-5.0
-
unknown authored
This fixes the problem if someone is using struct MYSQL as part of another structure together with a shared library include/mysql.h: Safer fix for Bug #18435 sql-common/client.c: Safer fix for Bug #18435
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-4.1
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/50-work ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp: Auto merged ndb/test/ndbapi/testNodeRestart.cpp: Auto merged ndb/test/src/NdbBackup.cpp: Auto merged ndb/test/src/NdbRestarts.cpp: Auto merged
-
unknown authored
Change semantic on DumpStateOrd::CmvmiSetRestartOnErrorInsert() Called wo/ args it resets to value in configuration (previously it set to 1 if called wo/ args) ndb/src/kernel/blocks/cmvmi/Cmvmi.cpp: Change semantic on DumpStateOrd::CmvmiSetRestartOnErrorInsert Called wo/ args it resets to value in configuration (previously it set to 1 if called wo/ args) ndb/test/ndbapi/testNodeRestart.cpp: Change semantic on DumpStateOrd::CmvmiSetRestartOnErrorInsert Called wo/ args it resets to value in configuration (previously it set to 1 if called wo/ args) ndb/test/src/NdbBackup.cpp: Change semantic on DumpStateOrd::CmvmiSetRestartOnErrorInsert Called wo/ args it resets to value in configuration (previously it set to 1 if called wo/ args) ndb/test/src/NdbRestarts.cpp: Change semantic on DumpStateOrd::CmvmiSetRestartOnErrorInsert Called wo/ args it resets to value in configuration (previously it set to 1 if called wo/ args)
-
unknown authored
netware/BUILD/compile-netware-START: added option for netware builds
-
- 24 Mar, 2006 13 commits
-
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
unknown authored
If the WHERE condition of a query contained an ORed FALSE term then the set of tables whose rows cannot serve for null complements in outer joins was determined incorrectly. It resulted in blocking possible conversions of outer joins into joins for such queries. mysql-test/r/join_outer.result: Added a test case for bug #17164. mysql-test/t/join_outer.test: Added a test case for bug #17164.
-
unknown authored
tables corrupt triggers". It turned out that we also have relied at certain places that (new_table != table_name) were always true on Windows and for transactional tables. Since our fix for the bug brakes this assumption we have to add new flag to pass this information around. This code needs to be refactored but I dare not to do this in 5.0. sql/sql_table.cc: mysql_alter_table(): Follow-up for the fix for bug #18153 "ALTER/OPTIMIZE/REPAIR on transactional tables corrupt triggers". It turned out that we also have relied at certain places that (new_table != table_name) were always true on Windows and for transactional tables. Since our fix for the bug brakes this assumption we have to add new flag to pass this information around. This code needs to be refactored but I dare not to do this in 5.0.
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
unknown authored
into mysql.com:/home/dlenev/mysql-5.0-bg18153
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0 mysql-test/lib/mtr_timer.pl: Auto merged ndb/src/ndbapi/NdbTransaction.cpp: Auto merged sql/ha_innodb.cc: Auto merged
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0
-
unknown authored
into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
-
unknown authored
into mysql.com:/home/dlenev/mysql-5.0-bg18153
-
unknown authored
triggers". Applying ALTER/OPTIMIZE/REPAIR TABLE statements to transactional table or to table of any type on Windows caused disappearance of its triggers. Bug was introduced in 5.0.19 by my fix for bug #13525 "Rename table does not keep info of triggers" (see comment for sql_table.cc for more info). . mysql-test/r/trigger.result: Added test-case covering handling of triggers when one does ALTER TABLE which should move table to different database. mysql-test/t/trigger.test: Added test-case covering handling of triggers when one does ALTER TABLE which should move table to different database. sql/sql_table.cc: mysql_alter_table(): Removal of strdup() which is no longer necessary allows us to preserve nice assumption that "(new_db != db || new_table != table_name) indicates that table will be renamed. So now we really can use this condition to avoid updating trigger definitions when table is not renamed. Note that we can't use (alter_info->flags & ALTER_RENAME) condition instead since it can be also true when we do "ALTER TABLE t1 RENAME TO t1". sql/sql_trigger.cc: Table_triggers_list::change_table_name(): Mentioned assumption that subject table is not renamed to itself in method description. Added DBUG_ASSERT() to catch wrong usage of this method. mysql-test/r/trigger-trans.result: New BitKeeper file ``mysql-test/r/trigger-trans.result'' mysql-test/t/trigger-trans.test: New BitKeeper file ``mysql-test/t/trigger-trans.test''
-
unknown authored
sql/udf_example.cc: Calculate length of returned string correctly
-
unknown authored
into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0
-
unknown authored
-
- 23 Mar, 2006 1 commit
-
-
unknown authored
Apparently libtool isn't properly setup on all our build hosts. mysql-test/mysql-test-run.pl: Only run in libtool if running in valgrind.
-