- 15 Jul, 2005 9 commits
-
-
unknown authored
test_client_character_set tests/mysql_client_test.c: minor fix for restoring the previous characterset.
-
unknown authored
into lmy002.wdf.sap.corp:/home/georg/work/mysql-5.0
-
unknown authored
When all rows are fetched subsequent calls to mysql_stmt_fetch return now MYSQL_NO_DATA instead of errorcode 1. libmysql/libmysql.c: fix for bug#11037 tests/mysql_client_test.c: added new testcase for bug #11037
-
unknown authored
into mysql.com:/usr/home/ram/work/mysql-5.0
-
unknown authored
-
unknown authored
sql/field.cc: a fix (bug #9881: ALTER TABLE gives wrong error message with sql-mode TRADITIONAL). Don't set def if NO_DEFAULT_VALUE_FLAG is set.
-
unknown authored
into mysql.com:/home/dlenev/src/mysql-5.0-bg9565
-
unknown authored
sub-sequent procedure is called" which was fixed by the same patch as bug #9597 "read lock stays when querying view from stored procedure". mysql-test/r/sp.result: Added test case for bug #9565 "Wrong locking in stored procedure if a sub-sequent procedure is called". mysql-test/t/sp.test: Added test case for bug #9565 "Wrong locking in stored procedure if a sub-sequent procedure is called".
-
unknown authored
-
- 14 Jul, 2005 31 commits
-
-
unknown authored
into sanja.is.com.ua:/home/bell/mysql/bk/work-bug4-5.0 mysql-test/r/view.result: Auto merged mysql-test/t/view.test: Auto merged
-
unknown authored
try to find most suitable table, to avouid pickup table with too low locking mode or occupy table with write mode for select when it will be need for update later (BUG#9597) mysql-test/r/view.result: opening table in correct locking mode test mysql-test/t/view.test: opening table in correct locking mode test sql/sql_base.cc: take into account table lock mode when opening table: try to find most suitable table, to avouid pickup table with too low locking mode or occupy table with write mode for select when it will be need for update later
-
unknown authored
into mysql.com:/opt/local/work/mysql-5.0-root mysql-test/t/ps.test: Manual merge
-
unknown authored
mysql-test/t/ps.test: Disable prepared statements for a part of the test to avoid result mismatch.
-
unknown authored
-
unknown authored
into mysql.com:/opt/local/work/mysql-5.0-root regex/regerror.c: Auto merged sql/sql_lex.cc: Auto merged mysql-test/r/ps.result: Manual merge mysql-test/t/ps.test: Manual merge sql/sql_yacc.yy: Manual merge
-
unknown authored
BitKeeper/deleted/.del-var~507a9bd3b926223e: Delete: mysql-test/var
-
unknown authored
into mysql.com:/opt/local/work/mysql-4.1-root
-
unknown authored
syntax in binlog which stops replication": disallow the use of parameter markers which can lead to generation of malformed binlog queries. mysql-test/r/ps.result: Test results fixed: a test case for Bug#11299 mysql-test/t/ps.test: A test case for Bug#11299 sql/sql_lex.cc: Introduce a new parser token for a parameter marker. Make sure that a parameter marker can not be used in a query which, when transformed to a binlog query, becomes grammatically incorrect. sql/sql_yacc.yy: The check for COM_PREPARE has been moved into the lexer. mysql-test/var: New BitKeeper file ``mysql-test/var''
-
unknown authored
into mysql.com:/media/sda1/mysql/mysql-5.0-10760-new
-
unknown authored
mysql-test/r/fulltext_order_by.result: A post-merge fix. mysql-test/t/fulltext_order_by.test: A post-merge fix (a different plan is chosen for a query in 5.0) sql/sql_select.cc: Post-merge fix.
-
unknown authored
into mysql.com:/media/sda1/mysql/mysql-5.0-10760-new sql/item_func.cc: Auto merged
-
unknown authored
into mysql.com:/opt/local/work/mysql-5.0-root
-
unknown authored
into linux.site:/home/reggie/bk/mysql-4.1
-
unknown authored
into mysql.com:/opt/local/work/mysql-5.0-root libmysql/libmysql.c: Manual merge tests/mysql_client_test.c: Manual merge
-
unknown authored
information about error". libmysql/libmysql.c: Clear the last error on the statement if mysql_stmt_reset succeeded. tests/mysql_client_test.c: A test case for Bug#11183 "mysql_stmt_reset() doesn't reset information about error"
-
unknown authored
into mysql.com:/opt/local/work/mysql-5.0-root mysql-test/r/ps_2myisam.result: Auto merged mysql-test/r/ps_3innodb.result: Auto merged mysql-test/r/ps_4heap.result: Auto merged mysql-test/r/ps_5merge.result: Auto merged mysql-test/r/ps_6bdb.result: Auto merged mysql-test/r/ps_7ndb.result: Auto merged sql/field.cc: manual merge tests/mysql_client_test.c: manual merge mysql-test/r/select.result: manual merge mysql-test/t/select.test: manual merge sql/sql_select.cc: Auto merged sql/item_func.cc: Auto merged
-
unknown authored
into mysql.com:/opt/local/work/mysql-4.1-root
-
unknown authored
into mysql.com:/home/psergey/mysql-4.1-merge-from-build sql/item_func.cc: Auto merged
-
unknown authored
ETIME was returned by cond_timedwait (sic, the pre-POSIX1001b function) on Solaris 2.6 and 2.7. pthread_cond_timedwait on Solaris returns ETIMEDOUT. The standard requirement is that the only additional return value of pthred_cond_timedwait compared to pthread_cond_wait is ETIMEDOUT. Let us not bloat the application code with redundant checks, and if we're ever to work on a platform that returns a non-standard value, we should write a wrapper for that platform (like we do, e.g., for Windows). mysys/my_os2cond.c: - fix our implementation of pthread_cond_timedwait on OS2 to return ETIMEDOUT instead of ETIME. sql/item_func.cc: - don't check for ETIME sql/slave.cc: - don't check for ETIME sql/sql_insert.cc: - don't check for ETIME
-
unknown authored
source table present (this happens for ORDER BY after UNION) mysql-test/r/fulltext_order_by.result: Testcase for BUG#11869 mysql-test/t/fulltext_order_by.test: Testcase for BUG#11869
-
unknown authored
This is needed because in some cases range optimization is performed twice and added NOT NULL item must have correct const_table_map() value. mysql-test/r/select.result: Testcase for BUG#11700 mysql-test/t/select.test: Testcase for BUG#11700
-
unknown authored
into deer.(none):/home/hf/work/mysql-5.0.clean
-
unknown authored
mysql-test/r/innodb.result: test result fixed mysql-test/r/type_newdecimal.result: test result fixed mysql-test/t/innodb.test: test moved here mysql-test/t/type_newdecimal.test: Innobase bug moved to the innodb.test
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.0
-
unknown authored
After merge fix. sql/item.cc: After merge fix.
-
unknown authored
into mysql.com:/media/sda1/mysql/mysql-5.0-10760-new
-
unknown authored
in cursors. libmysql/libmysql.c: - reset_stmt_handle(): don't reset the server side just because we have an open cursor: the server will close the cursor automatically if needed sql/sql_prepare.cc: - implement Prepared_statement::close_cursor, - implicitly close an open cursor in mysql_stmt_execute instead of issuing an error (to reduce the need to explicitly close cursors and save network bandwidth). - cleanup sql/sql_select.cc: Remove a destructor: cursor destruction can not be done by simply calling a destructor, because of cross-references between cursor and statement memory. sql/sql_select.h: - add an empty Cursor destructor tests/mysql_client_test.c: - remove a test for dropped functionality
-
unknown authored
into mysql.com:/opt/local/work/mysql-4.1-root
-
unknown authored
No separate typecode for MEDIUMTEXT/LONGTEXT is added, as we have no sound decision yet what typecodes and for what types are sent by the server (aka what constitutes a distinct type in MySQL). mysql-test/r/ps_2myisam.result: Test results fixed: new longtext/longblob length (2^32) mysql-test/r/ps_3innodb.result: Test results fixed: new longtext/longblob length (2^32) mysql-test/r/ps_4heap.result: Test results fixed: new longtext/longblob length (2^32) mysql-test/r/ps_5merge.result: Test results fixed: new longtext/longblob length (2^32) mysql-test/r/ps_6bdb.result: Test results fixed: new longtext/longblob length (2^32) mysql-test/r/ps_7ndb.result: Test results fixed: new longtext/longblob length (2^32) sql/field.cc: A fix for Bug#9735 "mysql_fetch_fields() acts strange on LONGBLOB/LONGTEXT": fix wrong initialization of field_length in case of BLOB fields. tests/mysql_client_test.c: A test case for Bug#9735 "mysql_fetch_fields() acts strange on LONGBLOB/LONGTEXT"
-
unknown authored
into mysql.com:/usr/home/bar/mysql-5.0 mysql-test/r/ctype_utf8.result: Auto merged mysql-test/t/ctype_utf8.test: Auto merged sql/item.h: Auto merged sql/sql_table.cc: Auto merged sql/item.cc: After merge fix.
-