- 12 Oct, 2007 9 commits
-
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.1-maint sql/mysqld.cc: Auto merged
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.1-maint
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
-
unknown authored
into polly.(none):/home/kaa/src/maint/bug31254/my51-bug31254 include/my_global.h: Auto merged
-
unknown authored
(compiler issue ?) Problem: Improper compile-time flags on AIX prevented use of files > 2 GB. This resulted in Max_data_length being truncated to 2 GB by MyISAM code. Solution: Reverted large-file changes from the fix for bug10776. We need to define _LARGE_FILES on AIX to have support for files > 2 GB. Since _LARGE_FILE_API is incompatible with _LARGE_FILES and may be automatically defined by including standards.h, we also need a workaround to avoid this conflict. config/ac-macros/large_file.m4: Reverted large-file changes from the fix for bug10776. We need to define _LARGE_FILES on AIX to have support for files > 2 GB. include/my_global.h: _LARGE_FILE_API is defined in standards.h that is automatically included by at least some C++ compilers on AIX. Since it is also incompatible with _LARGE_FILES which is required for POSIX IO calls to be largefile-safe, the only workaround is to explicitely #undef _LARGE_FILE_API.
-
unknown authored
into sin.intern.azundris.com:/home/tnurnberg/30821/51-30821 sql/mysqld.cc: Auto merged
-
unknown authored
into sin.intern.azundris.com:/home/tnurnberg/30821/50-30821 sql/mysqld.cc: Auto merged
-
unknown authored
into sin.intern.azundris.com:/home/tnurnberg/30821/51-30821 sql/mysqld.cc: NULL merge
-
unknown authored
Options to mysqld were not processed correctly because switch statement was missing some "break"s. CS adds them. No test case; would require .opt file and server restart. Manually tested. sql/mysqld.cc: Add missing "break"s to switch() in mysqld to fix option processing.
-
- 11 Oct, 2007 3 commits
-
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.1-maint
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.1-maint mysql-test/include/mix1.inc: Auto merged mysql-test/r/innodb_mysql.result: Auto merged
-
ssh://bk-internal.mysql.com//home/bk/mysql-5.0-maintunknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
-
- 10 Oct, 2007 15 commits
-
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51 mysql-test/mysql-test-run.pl: Auto merged scripts/mysql_system_tables_data.sql: Auto merged
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51 configure.in: Auto merged mysql-test/Makefile.am: Auto merged mysql-test/mysql-test-run.pl: Auto merged scripts/Makefile.am: Auto merged scripts/mysql_system_tables_data.sql: Auto merged scripts/mysqld_safe.sh: Auto merged sql/sql_select.cc: Auto merged storage/innobase/handler/ha_innodb.cc: Auto merged
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50 mysql-test/mysql-test-run.pl: Auto merged scripts/mysql_system_tables_data.sql: Auto merged
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51 sql/sql_class.cc: Auto merged
-
unknown authored
Introduced in mark_transaction_to_rollback(), part of fix for bug 24989; fix is to check thd for NULL before using it. sql/sql_class.cc: It is possible that mark_transaction_to_rollback() may be called in rare circumstances when thd is NULL (e.g., from some calls to convert_error_code_to_mysql()). Don't use thd if it is NULL.
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.1-maint
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.1-maint
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-5.0-maint
-
unknown authored
into polly.(none):/home/kaa/src/maint/mysql-4.1-maint
-
unknown authored
into polly.(none):/home/kaa/src/maint/bug28878/my51-bug28878 mysql-test/r/innodb_mysql.result: Auto merged sql/field.cc: Auto merged mysql-test/include/mix1.inc: Auto merged
-
unknown authored
into polly.(none):/home/kaa/src/maint/bug28878/my50-bug28878 mysql-test/r/innodb_mysql.result: Null merge. mysql-test/t/innodb_mysql.test: Null merge. sql/field.cc: Null merge.
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51
-
unknown authored
into mysql.com:/home/ram/work/b29444/b29444.5.1
-
unknown authored
client/mysqltest.c: Use correct data type for dummy variable passed to dirname_part()
-
- 09 Oct, 2007 13 commits
-
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51 sql/mysqld.cc: Auto merged sql/set_var.cc: Auto merged
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51 client/mysqldump.c: Auto merged mysys/my_init.c: Auto merged sql/mysqld.cc: Auto merged
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/50 sql/mysqld.cc: Auto merged
-
unknown authored
into mysql.com:/home/ram/work/mysql-5.1-maint
-
unknown authored
into mysql.com:/home/ram/work/mysql-5.1-maint mysql-test/r/grant.result: Auto merged mysql-test/r/type_datetime.result: manual merge. mysql-test/t/type_datetime.test: manual merge.
-
unknown authored
as PS protocol gives slightly different metadata.
-
unknown authored
into ramayana.hindu.god:/home/tsmith/m/bk/maint/51 sql/mysqld.cc: Use local (null merge) sql/set_var.cc: Use local (null merge) storage/innobase/handler/ha_innodb.cc: Use local (null merge) storage/innobase/handler/ha_innodb.h: Use local (null merge)
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
-
unknown authored
Problem: creating a partitioned table during name resolution for the partition function we search for column names in all parts of the CREATE TABLE query. It is superfluous (and wrong) sometimes. Fix: launch name resolution for the partition function against the table we're creating. mysql-test/r/partition.result: Fix for bug #29444: crash with partition refering to table in create-select - test result. mysql-test/t/partition.test: Fix for bug #29444: crash with partition refering to table in create-select - test result. sql/item.cc: Fix for bug #29444: crash with partition refering to table in create-select - LEX::use_only_table_context introduced, which is used in the Item_field::fix_fields() to resolve names only against context->first_name_resolution_table/last_name_resolution_table. sql/sql_lex.cc: Fix for bug #29444: crash with partition refering to table in create-select - LEX::use_only_table_context introduced, which is used in the Item_field::fix_fields() to resolve names only against context->first_name_resolution_table/last_name_resolution_table. sql/sql_lex.h: Fix for bug #29444: crash with partition refering to table in create-select - LEX::use_only_table_context introduced, which is used in the Item_field::fix_fields() to resolve names only against context->first_name_resolution_table/last_name_resolution_table. sql/sql_partition.cc: Fix for bug #29444: crash with partition refering to table in create-select - set the lex->use_only_table_context before the func_expr->fix_fields() call to ensure we're resolving names against the table we're creating; then restore it back after the call.
-
unknown authored
into mysql.com:/home/ram/work/b31438/b31438.5.1
-
unknown authored
into mysql.com:/home/ram/work/b31249/b31249.5.0 mysql-test/r/type_datetime.result: manual merge mysql-test/t/type_datetime.test: manual merge
-