- 06 Apr, 2006 21 commits
-
-
unknown authored
into april.(none):/home/svoj/devel/mysql/BUG14945/mysql-5.1-new mysql-test/mysql-test-run.pl: Auto merged mysql-test/r/sp.result: Auto merged mysql-test/t/sp.test: Auto merged sql/sql_parse.cc: Auto merged sql/sql_delete.cc: Manual merge
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.1-new
-
unknown authored
into april.(none):/home/svoj/devel/mysql/BUG14945/mysql-5.0
-
unknown authored
counter". When TRUNCATE TABLE was called within an stored procedure the auto_increment counter was not reset to 0 even if straight TRUNCATE for this table did this. This fix makes TRUNCATE in stored procedures to be handled exactly in the same way as straight TRUNCATE. We achieve this by rolling back the fix for bug 8850, which is no longer needed since stored procedures don't require prelocked mode anymore (and TRUNCATE is not allowed in stored functions or triggers). mysql-test/r/sp.result: Test case for BUG#14945. mysql-test/t/sp.test: Test case for BUG#14945. sql/sql_delete.cc: Handle TRUNCATE in stored procedures exactly in the same way as straight TRUNCATE (i.e. without falling back to DELETE if possible). We achieve this by rolling back the fix for bug 8850, which is no longer relevant since stored procedures don't require prelocked mode anymore (and TRUNCATE is not allowed in stored functions or triggers). sql/sql_parse.cc: Handle TRUNCATE in stored procedures exactly in the same way as straight TRUNCATE (i.e. without falling back to DELETE if possible). We achieve this by rolling back the fix for bug 8850, which is no longer relevant since stored procedures don't require prelocked mode anymore (and TRUNCATE is not allowed in stored functions or triggers).
-
unknown authored
into shellback.(none):/home/msvensson/mysql/mysql-5.1 client/mysqltest.c: Auto merged include/config-win.h: Auto merged include/m_ctype.h: Auto merged mysql-test/mysql-test-run.pl: Auto merged mysql-test/r/subselect.result: Auto merged sql/item_func.cc: Auto merged sql/opt_range.cc: Auto merged storage/csv/ha_tina.h: Auto merged strings/ctype-bin.c: Auto merged strings/ctype-euc_kr.c: Auto merged strings/ctype-gb2312.c: Auto merged strings/ctype-ucs2.c: Auto merged storage/csv/ha_tina.cc: SCCS merged
-
unknown authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.1-new libmysql/libmysql.c: Auto merged sql-common/client.c: Auto merged
-
unknown authored
as it is now required by mysql_set_character_set() libmysql/libmysql.c: Removing mysql_get_server_version() sql-common/client.c: Adding mysql_get_server_version()
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.1-new libmysql/libmysql.c: Auto merged sql-common/client.c: Auto merged
-
unknown authored
Bug#18830 incompatibility new libraries with old server Additional 5.0 fix: applying the same patch to client.c. sql-common/client.c: Bug#18830 incompatibility new libraries with old server Additional 5.0 fix: applying the same patch to client.c.
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.0 libmysql/libmysql.c: Bug#18830 incompatibility new libraries with old server Mergeing from 4.1
-
unknown authored
into mysql.com:/home/stewart/Documents/MySQL/5.1/new-bug18831
-
unknown authored
don't know why this didn't generate a warning, but let's fix it too. storage/ndb/src/common/debugger/signaldata/DictTabInfo.cpp: fix reversed memset
-
unknown authored
storage/ndb/src/common/debugger/signaldata/DictTabInfo.cpp: fix memset call initialize LF_UndoFreeWords(Hi|Lo)
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.1-new strings/ctype-extra.c: Auto merged
-
unknown authored
Bug#18830: incompatibility new libraries with old server Don't execute SET NAMES with pre-4.1 server. libmysql/libmysql.c: Bug#18830: incompatibility new libraries with old server Don't execute SET NAMES with pre-4.1 server.
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.0
-
unknown authored
Adding test case to cover queries which worked incorrectly earlier: Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci mysql-test/r/ctype_latin1.result: Adding test case for Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci mysql-test/t/ctype_latin1.test: Adding test case for Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci
-
unknown authored
Using local. strings/ctype-extra.c: Using local.
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.0 strings/conf_to_src.c: Auto merged
-
unknown authored
Backporting a 5.0 change: MAX_BUF was too small for Index.xml Changeing MAX_BUF and adding assert to easier catch the same problem in the future. ctype-extra.c: Regenerating ctype-extra.c with the fixed conf_to_src. strings/ctype-extra.c: Regenerating ctype-extra.c with the fixed conf_to_src. strings/conf_to_src.c: Backporting a 5.0 change: MAX_BUF was too small for Index.xml Changeing MAX_BUF and adding assert to easier catch the same problem in the future.
-
- 05 Apr, 2006 19 commits
-
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
-
unknown authored
into rurik.mysql.com:/home/igor/dev/mysql-5.1-0 mysql-test/r/view.result: Auto merged mysql-test/t/view.test: Auto merged sql/opt_sum.cc: Auto merged
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.1-new strings/ctype-extra.c: Auto merged
-
unknown authored
-
unknown authored
Recreating ctype-extra.c with additional 5.1 charset, and with additional missing 5.0 charset due to bug with too small buffer MAX_BUF. strings/ctype-extra.c: Recreating ctype-extra.c with additional 5.1 charset, and with additional missing 5.0 charset due to bug with too small buffer MAX_BUF.
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.1-new
-
unknown authored
Buffer was too small to load Index.xml. So some charsets were not gerenrated. Making the buffer bigger, and adding an DBUG_ASSERT, to easier catch the problem in the future. ctype-extra.c: Additional charsets were generated. strings/ctype-extra.c: Additional charsets were generated. strings/conf_to_src.c: Buffer was too small to load Index.xml. So some charsets were not gerenrated. Making the buffer bigger, and adding an DBUG_ASSERT, to easier catch the problem in the future.
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.1-new mysql-test/r/information_schema.result: Auto merged mysql-test/t/information_schema.test: Auto merged sql/item.cc: Auto merged sql/share/charsets/Index.xml: Auto merged storage/ndb/src/kernel/blocks/dbdih/DbdihMain.cpp: Auto merged storage/ndb/src/kernel/blocks/dbtc/DbtcMain.cpp: Auto merged
-
unknown authored
never defined. It was used at some point to add -Wuninitialized to debug flags, but not any more. If there is still need to add -Wunitialized, it can be added directly to $global_warnings. BUILD/compile-amd64-debug-max-no-ndb: Remove a no-op. BUILD/compile-amd64-debug-max: Remove a no-op. BUILD/compile-darwin-mwcc: Remove a no-op. BUILD/compile-pentium-debug-max-no-embedded: Remove a no-op. BUILD/compile-pentium-debug-max-no-ndb: Remove a no-op. BUILD/compile-pentium-debug-max: Remove a no-op. BUILD/compile-pentium-debug-openssl: Remove a no-op. BUILD/compile-pentium-debug-yassl: Remove a no-op. BUILD/compile-pentium-debug: Remove a no-op. BUILD/compile-pentium-mysqlfs-debug: Remove a no-op. BUILD/compile-pentium-valgrind-max: Remove a no-op. BUILD/compile-pentium64-debug-max: Remove a no-op. BUILD/compile-pentium64-debug: Remove a no-op. BUILD/compile-pentium64-valgrind-max: Remove a no-op. BUILD/compile-ppc-debug-max-no-ndb: Remove a no-op. BUILD/compile-ppc-debug-max: Remove a no-op. BUILD/compile-ppc-debug: Remove a no-op.
-
unknown authored
into mysql.com:/home/bk/b18436-mysql-5.1-new
-
unknown authored
into mysql.com:/home/bk/b18436-mysql-5.1-new
-
unknown authored
BUILD/SETUP.sh: Remove dead options. BUILD/compile-amd64-debug-max-no-ndb: Remove dead options. BUILD/compile-amd64-debug-max: Remove dead options. BUILD/compile-amd64-max: Remove dead options. BUILD/compile-darwin-mwcc: Remove dead options. BUILD/compile-pentium-debug-max-no-embedded: Remove dead options. BUILD/compile-pentium-debug-max-no-ndb: Remove dead options. BUILD/compile-pentium-debug-max: Remove dead options. BUILD/compile-pentium-icc-valgrind-max: Remove dead options. BUILD/compile-pentium-max: Remove dead options. BUILD/compile-pentium-valgrind-max: Remove dead options. There is no ISAM any more. BUILD/compile-pentium64-debug-max: Remove dead options. BUILD/compile-pentium64-valgrind-max: Remove dead options. There is no ISAM any more. BUILD/compile-ppc-debug-max-no-ndb: Remove dead options. BUILD/compile-ppc-debug-max: Remove dead options. BUILD/compile-ppc-max: Remove dead options.
-
unknown authored
After merge correction libmysqld/Makefile.am: After merge correction
-
unknown authored
into mysql.com:/home/bk/b18436-mysql-5.1-new
-
unknown authored
into sunlight.local:/local_work/16281-bug-5.0-mysql sql/field.h: Auto merged
-
unknown authored
Mutli-table uses temporary table to store new values for fields. With the new values the rowid of the record to be updated is stored in a Field_string field. Table to be updated is set as source table of the rowid field. But when the temporary table creates the tmp field for the rowid field it converts it to a varstring field because the table to be updated was created by the v4.1. Due to this the stored rowids were broken and no records for update were found. The flag can_alter_field_type is added to Field_string class. When it is set to 0 the field won't be converted to varstring. The Field_string::type() function now always returns MYSQL_TYPE_STRING if can_alter_field_type is set to 0. The multi_update::initialize_tables() function now sets can_alter_field_type flag to 0 for the rowid fields denying conversion of the field to a varstring field. sql/field.h: Fixed bug #16281: Multi-table update broken in 5.0 on tables imported from 4.1 The flag can_alter_field_type is added to Field_string class. When it is set to 0 the field won't be converted to varstring. The Field_string::type() function now always returns MYSQL_TYPE_STRING if can_alter_field_type is set to 0. sql/sql_update.cc: Fixed bug #16281: Multi-table update broken in 5.0 on tables imported from 4.1 The multi_update::initialize_tables() function now sets can_alter_field_type flag to 0 for the rowid fields denying conversion of the field to a varstring field.
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.1-new config/ac-macros/yassl.m4: Auto merged libmysql/Makefile.am: Auto merged libmysql_r/Makefile.am: Auto merged netware/BUILD/compile-linux-tools: Auto merged
-
unknown authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0 mysql-test/mysql-test-run.pl: Auto merged
-
unknown authored
into mysql.com:/home/bk/b18436-mysql-5.1-new
-