- 31 Aug, 2006 2 commits
- 30 Aug, 2006 6 commits
-
-
unknown authored
into maint2.mysql.com:/data/localhome/tsmith/bk/41
-
unknown authored
into maint2.mysql.com:/data/localhome/tsmith/bk/41 BUILD/SETUP.sh: Auto merged
-
unknown authored
-
unknown authored
-
unknown authored
into maint2.mysql.com:/data/localhome/tsmith/bk/bfx/41 BUILD/SETUP.sh: SCCS merged
-
unknown authored
Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte include/mysql_com.h: Bug#20393 User name truncation in mysql client Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte added new constants NAME_BYTE_LEN, USERNAME_BYTE_LENGTH, SYSTEM_CHARSET_MBMAXLEN mysql-test/r/ctype_utf8.result: Bug#20393 User name truncation in mysql client Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte test case mysql-test/t/ctype_utf8.test: Bug#20393 User name truncation in mysql client Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte test case sql-common/client.c: Bug#20393 User name truncation in mysql client Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte increased buffers for user name & db sql/sql_acl.cc: Bug#20393 User name truncation in mysql client Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte check that user name is not longer than USERNAME_LENGTH symbols sql/sql_parse.cc: Bug#20393 User name truncation in mysql client Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte increased buffers for user name & db sql/table.cc: Bug#20393 User name truncation in mysql client Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte check that db name is not longer than NAME_LEN symbols
-
- 29 Aug, 2006 1 commit
-
-
unknown authored
into maint2.mysql.com:/data/localhome/tsmith/bk/41
-
- 28 Aug, 2006 2 commits
- 27 Aug, 2006 1 commit
-
-
unknown authored
into moonbone.local:/work/tmp_merge-4.1-opt-mysql
-
- 26 Aug, 2006 2 commits
- 25 Aug, 2006 6 commits
-
-
unknown authored
Null merge to 5.0 mysql-test/mysql-test-run.pl: Ignore --skip-im if specified on command line
-
unknown authored
-
unknown authored
mysql-test/lib/mtr_cases.pl: Detect which tests that need ndb mysql-test/lib/mtr_match.pl: Add function mtr_match_substring mysql-test/mysql-test-run.pl: Only start cluster for test cases that need it
-
unknown authored
Default is "var/tmp" mysql-test/r/myisam.result: Update result file mysql-test/t/myisam.test: If running test suite with a non standard tmp dir, the "show create table" will print "DATA DIRECTORY=" Use replace_result to mask it out Set tmpdir to var/log to get the printout of DATA DIRECTORY also when running with standard tmpdir
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint
-
unknown authored
mysql-test/lib/mtr_misc.pl: On windows the exe does not need to be executable for it to be found
-
- 24 Aug, 2006 6 commits
-
-
unknown authored
mysql-test/r/subselect.result: BUG#16255: A proper testcase mysql-test/t/subselect.test: BUG#16255: A proper testcase
-
unknown authored
Must not use Item_direct_ref in HAVING because it points to the new value (witch is not yet calculated for the first row). mysql-test/r/subselect.result: Bug #16255: Subquery in where - test case mysql-test/t/subselect.test: Bug #16255: Subquery in where - test case sql/item_subselect.cc: Bug #16255: Subquery in where Must not use Item_direct_ref in HAVING because it points to the new value (witch is not yet calculated for the first row).
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-4.1-maint support-files/mysql.spec.sh: Auto merged
-
unknown authored
into maint1.mysql.com:/data/localhome/tsmith/bk/41
-
unknown authored
into siva.hindu.god:/usr/home/tim/m/bk/41 sql/item_func.h: Auto merged sql/item_strfunc.cc: Auto merged
-
unknown authored
- Fix typo in Item_func_export_set::fix_length_and_dec() which caused character set aggregation to fail - Remove default argument from last arg of agg_arg_charsets() function, to reduce potential errors mysql-test/r/func_misc.result: Test EXPORT_SET() with charset coersion (bug #21531) mysql-test/t/func_misc.test: Test EXPORT_SET() with charset coersion (bug #21531) sql/item_func.h: Remove default argument from last arg of agg_arg_charsets() function, to reduce potential errors. sql/item_strfunc.cc: Fix typo in Item_func_export_set::fix_length_and_dec() which caused character set aggregation to fail.
-
- 23 Aug, 2006 5 commits
-
-
unknown authored
into siva.hindu.god:/usr/home/tim/m/bk/41 sql/item_strfunc.cc: Auto merged sql/item_strfunc.h: Auto merged sql/slave.cc: Auto merged sql/sql_acl.cc: Auto merged
-
unknown authored
Remove some sql_print_error() calls which were triggered by user error (i.e., not server-level events at all). Also, convert an sql_print_error -> sql_print_information for a non-error server event. sql/slave.cc: Change sql_print_error to sql_print_information for non-error status message. sql/sql_acl.cc: Remove sql_print_error calls for events which are not server errors
-
unknown authored
into maint1.mysql.com:/data/localhome/tsmith/bk/41
-
unknown authored
into lamia.home:/home/timka/mysql/src/4.1-bug-21456 sql/sql_select.cc: Auto merged
-
unknown authored
GROUP BY/DISTINCT pruning optimization must be done before ORDER BY optimization because ORDER BY may be removed when GROUP BY/DISTINCT sorts as a side effect, e.g. in SELECT DISTINCT <non-key-col>,<pk> FROM t1 ORDER BY <non-key-col> DISTINCT must be removed before ORDER BY as if done the other way around it will remove both. mysql-test/r/distinct.result: Test for BUG#21456. mysql-test/t/distinct.test: Test for BUG#21456. sql/sql_select.cc: Bug #21456: SELECT DISTINCT(x) produces incorrect results when using order by GROUP BY/DISTINCT pruning optimization must be done before ORDER BY optimization because ORDER BY may be removed when GROUP BY/DISTINCT sorts as a side effect.
-
- 22 Aug, 2006 1 commit
-
-
unknown authored
Added ndb_size.{pl,tmpl} to the RPM install (bug#20426) support-files/mysql.spec.sh: Added ndb_size.{pl,tmpl} to the RPM install (bug#20426)
-
- 19 Aug, 2006 2 commits
- 17 Aug, 2006 1 commit
-
-
unknown authored
into mysql.com:/usr/home/ram/work/4.1.b20695
-
- 16 Aug, 2006 3 commits
-
-
unknown authored
mysql-test/r/mysql_client.result: Removed OS dependant output. mysql-test/t/mysql_client.test: Re-directed output to a temporary file because the actual output isn't important and was causing a Windows test failure.
-
unknown authored
into mysql.com:/usr/home/bar/mysql-4.1.b9509
-
unknown authored
into mysql.com:/usr/home/bar/mysql-4.1.b9509 mysql-test/r/ctype_utf8.result: Auto merged mysql-test/t/ctype_utf8.test: Auto merged sql/sql_select.cc: Auto merged
-
- 15 Aug, 2006 2 commits
-
-
unknown authored
BUG#21077: Possible crash caused by invalid sequence of handler::* calls: The crash was caused by invalid sequence of handler::** calls: ha_smth->index_init(); ha_smth->index_next_same(); (2) (2) is an invalid call as it was not preceeded by any 'scan setup' call like index_first() or index_read(). The cause was that QUICK_SELECT::reset() didn't "fully reset" the quick select- current QUICK_RANGE wasn't forgotten, and quick select might attempt to continue reading the range, which would result in the above mentioned invalid sequence of handler calls. 5.x versions are not affected by the bug - they already have the missing "range=NULL" clause. mysql-test/r/innodb_mysql.result: Testcase for BUG#21077 mysql-test/t/innodb_mysql.test: Testcase for BUG#21077 sql/opt_range.h: BUG#21077: Possible crash caused by invalid sequence of handler::* calls: - Make QUICK_SELECT::reset() really reset the quick select
-
unknown authored
into mysql.com:/windows/Linux_space/MySQL/mysql-4.1
-