- 01 Sep, 2006 1 commit
-
-
unknown authored
into maint2.mysql.com:/data/localhome/tsmith/bk/50 mysql-test/r/heap_btree.result: Auto merged sql/set_var.cc: Auto merged mysql-test/t/heap_btree.test: Manual merge.
-
- 31 Aug, 2006 11 commits
-
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint tests/mysql_client_test.c: Auto merged
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/no-strange-literals/my50-no-strange-literals tests/mysql_client_test.c: Auto merged
-
unknown authored
single file is a bad practice. tests/mysql_client_test.c: Replace literal characters which don't make sense in UTF8 with ubiquitously- understood numbers.
-
unknown authored
extra/yassl/include/openssl/generate_prefix_files.pl: Allow a '*' to be together with the function name. As in this example: "BIGNUM *BN_bin2bn"
-
unknown authored
- Don't add the signatures for CRYPTO_* when compiling yaSSL for MySQL extra/yassl/taocrypt/src/misc.cpp: No need to include the CRYPTO_* when compiling yaSSL for MySQL
-
unknown authored
- Correct bug in perl script that faild to add rename macros for some functions. extra/yassl/include/openssl/prefix_ssl.h: Add prefixes for a bunch of new functions found with the new version of generate_prefix_files.pl
-
unknown authored
into shellback.(none):/home/msvensson/mysql/mysql-5.0-maint configure.in: Auto merged include/mysql.h: Auto merged include/mysql_com.h: Auto merged sql-common/client.c: Auto merged sql/item_strfunc.cc: Auto merged sql/item_strfunc.h: Auto merged sql/sql_acl.cc: Auto merged
-
unknown authored
mysql-test/r/ctype_ucs.result: Update result file mysql-test/t/ctype_ucs.test: Disable testing of "encrypt" function in this file. That test has to be guarded by "have_crypt.inc"
-
unknown authored
into bodhi.local:/opt/local/work/mysql-5.0-14897 configure.in: Auto merged include/mysql_com.h: Auto merged mysql-test/r/grant.result: Auto merged mysql-test/r/sp.result: Auto merged mysql-test/r/trigger.result: Auto merged mysql-test/r/view.result: Auto merged mysql-test/t/grant.test: Auto merged mysql-test/t/sp.test: Auto merged mysql-test/t/trigger.test: Auto merged mysql-test/t/view.test: Auto merged sql/mysql_priv.h: Auto merged sql/sql_acl.cc: Auto merged sql/sql_parse.cc: Auto merged sql/share/errmsg.txt: Auto merged sql/sql_yacc.yy: Auto merged
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug04053/my50-bug04053
-
- 30 Aug, 2006 14 commits
-
-
unknown authored
into maint2.mysql.com:/data/localhome/tsmith/bk/50 sql-common/client.c: Auto merged sql/item_func.h: Auto merged BUILD/check-cpu: Manual merge
-
unknown authored
into maint2.mysql.com:/data/localhome/tsmith/bk/50
-
unknown authored
into zippy.cornsilk.net:/home/cmiller/work/mysql/bug04053/my41-bug04053 mysys/my_read.c: Auto merged
-
unknown authored
event' from master" Since there is no repeatable test case, and this is obviously wrong, this is the most conservative change that might possibly work. The syscall read() wasn't checked for a negative return value for an interrupted read. The kernel sys_read() returns -EINTR, and the "library" layer maps that to return value of -1 and sets errno to EINTR. It's impossible (on Linux) for read() to set errno EINTR without the return value being -1 . So, if we're checking for EINTR behavior, we should not require that the return value be zero. mysys/my_read.c: The read() syscall should check for negative one, since that (usually) signals errors (like being interrupted) and zero (usually) signals end-of-file .
-
unknown authored
into maint2.mysql.com:/data/localhome/tsmith/bk/bfx/50 BUILD/SETUP.sh: Auto merged mysql-test/r/ctype_ucs.result: Auto merged mysql-test/t/ctype_ucs.test: Auto merged BUILD/check-cpu: Manual merge.
-
unknown authored
-
unknown authored
into bodhi.local:/opt/local/work/mysql-5.0-14897 sql/mysqld.cc: Auto merged
-
unknown authored
-
unknown authored
into maint2.mysql.com:/data/localhome/tsmith/bk/bfx/41 BUILD/SETUP.sh: SCCS merged
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0 sql-common/client.c: Auto merged
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0 include/mysql.h: SCCS merged include/mysql_com.h: SCCS merged sql-common/client.c: SCCS merged
-
unknown authored
into neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint tests/mysql_client_test.c: SCCS merged
-
unknown authored
- Use the "%.*b" format when printing prepared and exeuted prepared statements to the log. - Add test case to check that also prepared statements end up in the query log Bug#14346 Prepared statements corrupting general log/server memory - Use "stmt->query" when logging the newly prepared query instead of "packet" sql/sql_prepare.cc: mysql_stmt_prepare - Use "%.*b" format when printing to log - Print the query from stmt instead of "packet", packet points at the net in/out buffer and has most likely been overwritten when result for prepare was written to client. mysql_stmt_execute - Use "%.*b" format when printing to log - Print the query from thd as the expanded query has been specifially set to be valid also after restore from backup statement tests/mysql_client_test.c: Add tests for bug#21813 to already existing test for bug#17667. Add functionality for also executing prepared statements and making sure they end up in the log as well.
-
unknown authored
Auto merged include/config-netware.h: Auto merged sql/sql_base.cc: Auto merged
-
- 29 Aug, 2006 11 commits
-
-
unknown authored
mysql-test/r/view.result: A post-merge fix. mysql-test/t/grant.test: A post-merge fix. mysql-test/t/view.test: A post-merge fix.
-
unknown authored
into mysql.com:/Users/kent/mysql/bk/mysql-5.0
-
unknown authored
length limit", it's superseded by the fix for Bug#16899 "Possible buffer overflow in handling of DEFINER-clause". Update test results. mysql-test/r/grant.result: A post-merge fix. mysql-test/t/grant.test: A new error is returned, use the default database after drop database. sql/sql_acl.cc: Remove an unneeded check.
-
unknown authored
into bodhi.local:/opt/local/work/mysql-5.0-14897 configure.in: Auto merged mysql-test/mysql-test-run.pl: Auto merged mysql-test/r/im_life_cycle.result: Auto merged mysql-test/t/im_life_cycle.imtest: Auto merged sql/field.cc: Auto merged sql/item.cc: Auto merged sql/item.h: Auto merged sql/item_cmpfunc.cc: Auto merged sql/item_func.cc: Auto merged sql/item_strfunc.cc: Auto merged sql/item_strfunc.h: Auto merged sql/mysql_priv.h: Auto merged sql/mysqld.cc: Auto merged sql/sql_acl.cc: Auto merged sql/sql_class.cc: Auto merged sql/sql_parse.cc: Auto merged sql/sql_view.cc: Auto merged sql/sql_yacc.yy: Auto merged sql/share/errmsg.txt: Auto merged mysql-test/r/grant.result: Manual merge. mysql-test/r/view.result: Manual merge. mysql-test/t/grant.test: Manual merge. mysql-test/t/view.test: Manual merge.
-
unknown authored
doesn't find the column" When a user was using 4.1 tables with VARCHAR column and 5.0 server and a query that used a temporary table to resolve itself, the table metadata for the varchar column sent to client was incorrect: MYSQL_FIELD::table member was empty. The bug was caused by implicit "upgrade" from old VARCHAR to new VARCHAR hard-coded in Field::new_field, which did not preserve the information about the original table. Thus, the field metadata of the "upgraded" field pointed to an auxiliary temporary table created for query execution. The fix is to copy the pointer to the original table to the new field. mysql-test/r/type_varchar.result: Update test results (Bug#14897) mysql-test/t/type_varchar.test: Add a test case for Bug#14897 "ResultSet.getString("table.column") sometimes doesn't find the column" sql/field.cc: Preserve the original table name when converting fields from old VARCHAR to new VARCHAR. mysql-test/std_data/14897.frm: New BitKeeper file ``mysql-test/std_data/14897.frm''
-
unknown authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-kt
-
unknown authored
into polly.local:/home/kaa/src/maint/m50-maint--07OGt
-
unknown authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug17591
-
unknown authored
- BUG#15934: Instance manager fails to work; - BUG#18020: IM connect problem; - BUG#18027: IM: Server_ID differs; - BUG#18033: IM: Server_ID not reported; - BUG#21331: Instance Manager: Connect problems in tests; The only test suite has been changed (server codebase has not been modified). BitKeeper/deleted/.del-im_check_os.inc: Rename: mysql-test/include/im_check_os.inc -> BitKeeper/deleted/.del-im_check_os.inc mysql-test/include/im_check_env.inc: Include only this file from all IM-tests. mysql-test/lib/mtr_io.pl: Update mtr_get_pid_from_file() to workaround race, described in BUG#21884. mysql-test/lib/mtr_process.pl: Refactor im_start()/im_stop() so that they will be more reliable. There are the following user-visible changes: - if one of these functions fails, the test suite is aborted; - mtr_im_stop() now determines whether the component is alive or not not only by checking PID, but also by trying to connect to the component; - after starting IM, the test suite waits for it to start accepting client connections and to start all its guarded mysqld instances; - a lot of debug-logs have been added in order to simplify investigation of future failures. mysql-test/mysql-test-run.pl: 1. Get rid of kill_and_cleanup(); 2. Move im_start()/im_stop() to mtr_process.pl; 3. Change default IM port to 9311 so that it does not interfere with default slave port; mysql-test/r/im_daemon_life_cycle.result: Updated result file. mysql-test/r/im_life_cycle.result: Updated result file. mysql-test/r/im_options_set.result: Updated result file. mysql-test/r/im_options_unset.result: Updated result file. mysql-test/r/im_utils.result: Updated result file. mysql-test/t/im_daemon_life_cycle.imtest: Updated IM-test. mysql-test/t/im_life_cycle.imtest: Updated IM-test. mysql-test/t/im_options_set.imtest: Updated IM-test. mysql-test/t/im_options_unset.imtest: Updated IM-test. mysql-test/t/im_utils.imtest: Updated IM-test.
-
unknown authored
into moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug17591 mysql-test/r/view.result: Manual merge. mysql-test/t/view.test: Manual merge.
-
unknown authored
When a view was used inside a trigger or a function, lock type for tables used in a view was always set to READ (thus making the view non-updatable), even if we were trying to update the view. The solution is to set lock type properly. mysql-test/r/view.result: Add result for bug#17591: Updatable view not possible with trigger or stored function. mysql-test/t/view.test: Add test case for bug#17591: Updatable view not possible with trigger or stored function. sql/sql_view.cc: Move the code that sets requested lock type before the point where we exit from mysql_make_view() when we process a placeholder for prelocked table.
-
- 28 Aug, 2006 3 commits
-
-
unknown authored
-
unknown authored
init_dumping now accepts a function pointer to the table or view specific init_dumping function. This allows both tables and views to use the init_dumping function. client/mysqldump.c: Added functions for table and view specific dumping initalization. mysql-test/r/mysqldump.result: Added Result. mysql-test/t/mysqldump.test: Added test case.
-
unknown authored
into bk-internal.mysql.com:/data0/bk/mysql-5.0-kt
-