summaryrefslogtreecommitdiff
path: root/mysql-test/t
Commit message (Collapse)AuthorAgeFilesLines
* Merge mysql.com:/home/tomash/src/mysql_ab/mysql-5.0kroki@mysql.com2006-04-131-0/+28
|\ | | | | | | into mysql.com:/home/tomash/src/mysql_ab/mysql-5.0-bug15933
| * Bug#16461: connection_id() does not work properly inside triggerkroki@mysql.com2006-04-121-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | CONNECTION_ID() was implemented as a constant Item, i.e. an instance of Item_static_int_func class holding value computed at creation time. Since Items are created on parsing, and trigger statements are parsed on table open, the first connection to open a particular table would effectively set its own CONNECTION_ID() inside trigger statements for that table. Re-implement CONNECTION_ID() as a class derived from Item_int_func, and compute connection_id on every call to fix_fields().
* | In test for bug#15933 we have to wait for all disconnects to finish to avoidkroki@mysql.com2006-04-121-14/+51
|/ | | | | | a race between updating and checking Max_used_connections. This is done in a loop until either disconnect finished or timeout expired. In a latter case the test will fail.
* Bug#15933: max_used_connections is wrong after FLUSH STATUS if connections ↵kroki@mysql.com2006-04-071-1/+64
| | | | | | | | | | | | | | | | are cached After FLUSH STATUS max_used_connections was reset to 0, and haven't been updated while cached threads were reused, until the moment a new thread was created. The first suggested fix from original bug report was implemented: a) On flushing the status, set max_used_connections to threads_connected, not to 0. b) Check if it is necessary to increment max_used_connections when taking a thread from the cache as well as when creating new threads
* Merge mysql.com:/home/timka/mysql/src/5.0-virgintimour@mysql.com2006-03-311-0/+8
|\ | | | | | | into mysql.com:/home/timka/mysql/src/5.0-bug-16710
| * Fix for BUG#16710.timour@mysql.com2006-03-311-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The bug was due to a missed case in the detection of whether an index can be used for loose scan. More precisely, the range optimizer chose to use loose index scan for queries for which the condition(s) over an index key part could not be pushed to the index together with the loose scan. As a result, loose index scan was selecting the first row in the index with a given GROUP BY prefix, and was applying the WHERE clause after that, while it should have inspected all rows with the given prefix, and apply the WHERE clause to all of them. The fix detects and skips such cases.
* | Merge rurik.mysql.com:/home/igor/mysql-5.0igor@rurik.mysql.com2006-03-301-0/+52
|\ \ | | | | | | | | | into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
| * | Fixed bug #18279: crash in the cases when on conditions are moved igor@rurik.mysql.com2006-03-291-0/+52
| | | | | | | | | | | | | | | | | | | | | | | | | | | out of a nested join to the on conditions for the nest. The bug happened due to: 1. The function simplify_joins could change on expressions for nested joins. Yet modified on expressions were not saved in prep_on_expr. 2. On expressions were not restored for nested joins in reinit_stmt_before_use.
* | | Manual mergeevgen@sunlight.local2006-03-302-0/+42
|\ \ \
| * \ \ Merge epotemkin@bk-internal.mysql.com:/home/bk/mysql-4.1evgen@sunlight.local2006-03-301-0/+8
| |\ \ \ | | | | | | | | | | | | | | | into sunlight.local:/local_work/15560-bug-4.1-mysql
| | * | | Fixed bug#15560: GROUP_CONCAT wasn't ready for WITH ROLLUP queriesevgen@moonbone.local2006-03-291-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GROUP_CONCAT uses its own temporary table. When ROLLUP is present it creates the second copy of Item_func_group_concat. This copy receives the same list of arguments that original group_concat does. When the copy is set up the result_fields of functions from the argument list are reset to the temporary table of this copy. As a result of this action data from functions flow directly to the ROLLUP copy and the original group_concat functions shows wrong result. Since queries with COUNT(DISTINCT ...) use temporary tables to store the results the COUNT function they are also affected by this bug. The idea of the fix is to copy content of the result_field for the function under GROUP_CONCAT/COUNT from the first temporary table to the second one, rather than setting result_field to point to the second temporary table. To achieve this goal force_copy_fields flag is added to Item_func_group_concat and Item_sum_count_distinct classes. This flag is initialized to 0 and set to 1 into the make_unique() member function of both classes. To the TMP_TABLE_PARAM structure is modified to include the similar flag as well. The create_tmp_table() function passes that flag to create_tmp_field(). When the flag is set the create_tmp_field() function will set result_field as a source field and will not reset that result field to newly created field for Item_func_result_field and its descendants. Due to this there will be created copy func to copy data from old result_field to newly created field.
| * | | | Fix error in prefix compression of keys in MyISAM when key length changed ↵monty@mysql.com2006-03-301-0/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from 254 -> 255 Bug #17705 "FT Index corruption occurs with UTF8 data..." (Actually, the bug had nothing to do with FT index but with general key compression)
* | | | | post-merge fixgluh@eagle.intranet.mysql.r18.ru2006-03-301-1/+1
| | | | |
* | | | | Mergegluh@mysql.com2006-03-301-0/+6
|\ \ \ \ \ | |/ / / /
| * | | | Fix for bug#15316 SET value having comma not correctly handledgluh@eagle.intranet.mysql.r18.ru2006-03-291-0/+6
| | | | | | | | | | | | | | | | | | | | disallow the use of comma in SET members
| * | | | Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-4.1bar@mysql.com2006-03-281-0/+9
| |\ \ \ \ | | | | | | | | | | | | | | | | | | into mysql.com:/usr/home/bar/mysql-4.1.b15098
| * \ \ \ \ Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-4.1bar@mysql.com2006-03-233-0/+35
| |\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | into mysql.com:/usr/home/bar/mysql-4.1.b15376
| * \ \ \ \ \ Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-4.1bar@mysql.com2006-03-231-0/+30
| |\ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | into mysql.com:/usr/home/bar/mysql-4.1.b17374
* | \ \ \ \ \ \ Merge bk-internal.mysql.com:/home/bk/mysql-5.0konstantin@mysql.com2006-03-305-3/+151
|\ \ \ \ \ \ \ \ | |_|_|_|_|_|/ / |/| | | | | | | | | | | | | | | into mysql.com:/opt/local/work/mysql-5.0-15683
| * | | | | | | Merge bk-internal.mysql.com:/home/bk/mysql-5.0-runtimedlenev@mysql.com2006-03-291-0/+34
| |\ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | into mysql.com:/home/dlenev/mysql-5.0-bg17764
| | * | | | | | | Proposed fix for bug #17764 "Trigger crashes MyISAM table"dlenev@mysql.com2006-03-291-0/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A table with an on insert trigger was reported as crashed when the insert was processed with bulk insert mode on (handler::start_bulk_insert). The trigger was also selecting from the same table, and that caused the "crash". The same problem was present when an insert statement, which was processed in bulk mode, also used a stored function that was reading the same table. This fix disables bulk inserts if a statement uses functions or invokes triggers. Implementing more granular checks will require much more code and therefore can hardly be done in 5.0
| * | | | | | | | Merge mysql.com:/extern/mysql/bk/mysql-5.0-runtimepem@mysql.com2006-03-281-3/+16
| |\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into mysql.com:/extern/mysql/5.0/bug17015/mysql-5.0-runtime
| | * \ \ \ \ \ \ \ Merge mysql.com:/extern/mysql/bk/mysql-5.0-runtimepem@mysql.com2006-03-281-3/+16
| | |\ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into mysql.com:/extern/mysql/5.0/bug17015/mysql-5.0-runtime
| | | * | | | | | | | Fixed BUG#17015: Routine name truncation not an errorpem@mysql.com2006-02-161-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The name length was checked "the old way", not taking charsets into account, when creating a stored routine. Fixing this enforces the real limit (64 characters) again, and no truncation is possible.
| * | | | | | | | | | Merge mysql.com:/extern/mysql/bk/mysql-5.0-runtimepem@mysql.com2006-03-282-0/+70
| |\ \ \ \ \ \ \ \ \ \ | | |/ / / / / / / / / | |/| | | | | | | | | | | | | | | | | | | | into mysql.com:/extern/mysql/5.0/bug16474/mysql-5.0-runtime
| | * | | | | | | | | Post review fixes for BUG#16474: SP crashed MySQL.pem@mysql.com2006-03-282-0/+39
| | | | | | | | | | |
| | * | | | | | | | | Fixed BUG#16474: SP crashed MySQLpem@mysql.com2006-03-101-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fix_fields() was not called for "order by" variables if the type was a "constant integer", and thus interpreted as a column index. However, a local variable is an expression and should not be interpreted as a column index. Instead it behaves just like when using a user variable for instance (i.e. it will not affect the ordering).
| * | | | | | | | | | A fix and a test case for Bug#15683 "crash, Function on nested konstantin@mysql.com2006-03-281-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | VIEWs, Prepared statement": we didn't mark the nested views as 'prelockng placeholders' when building the prelocking list. This resulted in these views being processed (merged, materialized) before they are actually used.
* | | | | | | | | | | Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-5.0aivanov@mysql.com2006-03-301-0/+1
|\ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into mysql.com:/home/alexi/innodb/mysql-5.0-merge
| * | | | | | | | | | | Restoring changes erroneously removed by applyingaivanov@mysql.com2006-03-301-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the innodb-5.0-ss368 snapshot.
| * | | | | | | | | | | Merge aivanov@bk-internal.mysql.com:/home/bk/mysql-5.0aivanov@mysql.com2006-03-291-3/+1
| |\ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into mysql.com:/home/alexi/innodb/mysql-5.0-merge
| | * | | | | | | | | | | Applied innodb-5.0-ss368 snapshotaivanov@mysql.com2006-03-291-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixed bugs: #16814: SHOW INNODB STATUS format error in LATEST FOREIGN KEY ERROR section dict_foreign_key_error_report(): Always print a newline after invoking dict_print_info_on_foreign_key_in_create_format(). #16827: Better InnoDB error message if ibdata files omitted from my.cnf. #17126: CHECK TABLE on InnoDB causes a short hang during check of adaptive hash. CHECK TABLE blocking other queries, by releasing the btr_search_latch periodically during the adaptive hash table validation. #17405: Valgrind: conditional jump or move depends on uninitialised valuesw. buf_block_init(): Reset magic_n, buf_fix_count, and io_fix to avoid testing uninitialised variables. #18077: InnoDB uses full explicit table locks in stored FUNCTION. #18238: When locks exhaust the buffer pool, InnoDB does not roll back the trx. Check in pessimistic insert and update if the buffer pool is exhausted by locks. #18252: Disk space leaks in updates of InnoDB BLOB rows. btr_cur_pessimistic_update(): Invoke rec_get_offset() after rec_set_field_extern_bits(). btr_store_big_rec_extern_fields(): Note that offsets will no longer be valid after calling this function. #18283: When InnoDB returns error 'lock table full', MySQL can write to binlog too much. #18384: InnoDB memory leak on duplicate key errors if row has many columns. row_ins_duplicate_error_in_clust(): Call mem_heap_free(heap) at func_exit if needed. #18350: Use consistent read in CREATE ... SELECT .. if innodb_locks_unsafe_for_binlog is used.
* | | | | | | | | | | | | Reverting yesterday's patch. (cmiller:1.2099)cmiller@zippy.(none)2006-03-291-22/+0
|/ / / / / / / / / / / /
* | | | | | | | | | | | Merge bk-internal.mysql.com:/home/bk/mysql-5.0cmiller@zippy.(none)2006-03-281-0/+22
|\ \ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into zippy.(none):/home/cmiller/work/mysql/mysql-5.0__bug11151
| * | | | | | | | | | | | Bug#11151: LOAD DATA INFILE commits transaction in 5.0cmiller@zippy.(none)2006-03-281-0/+22
| | |/ / / / / / / / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | No longer create or commit transactions within the loading of files.
* | | | | | | | | | | | Merge abarkov@bk-internal.mysql.com:/home/bk/mysql-5.0bar@mysql.com2006-03-281-0/+38
|\ \ \ \ \ \ \ \ \ \ \ \ | |_|/ / / / / / / / / / |/| | | | | | | | | | | | | | | | | | | | | | | into mysql.com:/usr/home/bar/mysql-5.0
| * | | | | | | | | | | Merge joreland@bk-internal.mysql.com:/home/bk/mysql-5.0jonas@perch.ndb.mysql.com2006-03-281-0/+38
| |\ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
| | * \ \ \ \ \ \ \ \ \ \ Merge perch.ndb.mysql.com:/home/jonas/src/50-workjonas@perch.ndb.mysql.com2006-03-281-0/+38
| | |\ \ \ \ \ \ \ \ \ \ \ | | | |/ / / / / / / / / / | | |/| | | | | | | | | | | | | | | | | | | | | | | into perch.ndb.mysql.com:/home/jonas/src/mysql-5.0
| | | * | | | | | | | | | ndb - bug#17729 bug#18406jonas@perch.ndb.mysql.com2006-03-281-0/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ndbapi can reorder recattr when doing sorted scan (for faster comparision) make sure handler maps correct recattr to correct mysql column
* | | | | | | | | | | | | Merge mysql.com:/usr/home/bar/mysql-4.1.b15098bar@mysql.com2006-03-281-0/+9
|\ \ \ \ \ \ \ \ \ \ \ \ \ | |/ / / / / / / / / / / / |/| | | | | | | | | / / / | | |_|_|_|_|_|_|_|/ / / | |/| | | | | | | | | | into mysql.com:/usr/home/bar/mysql-5.0 Bug#15098
| * | | | | | | | | | | Bug#15098 CAST(column double TO signed int), wrong resultbar@mysql.com2005-12-061-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | field.cc: Adding longlong range checking to return LONGLONG_MIN or LONGLONG_MAX when out of range. Using (longlong) cast only when range is ok. cast.test: Adding test case. cast.result: Fixing results accordingly.
* | | | | | | | | | | | Added tests with IGNORE and NULL valuesmskold@mysql.com2006-03-281-0/+8
| | | | | | | | | | | |
* | | | | | | | | | | | Fix for Bug #15722 Engine_condition_pushdown fails when using blobs(text)mskold@mysql.com2006-03-281-1/+11
| | | | | | | | | | | |
* | | | | | | | | | | | Merge ibabaev@bk-internal.mysql.com:/home/bk/mysql-5.0igor@rurik.mysql.com2006-03-271-0/+14
|\ \ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into rurik.mysql.com:/home/igor/mysql-5.0
| * | | | | | | | | | | | Fixed bug #18386.igor@rurik.mysql.com2006-03-271-0/+14
| | |/ / / / / / / / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An invalid assertion in Item_direct_view_ref::eq caused an assertion abort in the debug version.
* | | | | | | | | | | | Disable udf testian@zim.(none)2006-03-271-0/+1
|/ / / / / / / / / / /
* | | | | | | | | | | Test case for BUG#15102 : select distinct returns empty result, select count ↵gkodinov@mysql.com2006-03-271-0/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | distinct > 0 (correct) Reproduced in 5.0.16-nt. Tested to work in 5.0.20
* | | | | | | | | | | Merge rurik.mysql.com:/home/igor/mysql-5.0igor@rurik.mysql.com2006-03-241-0/+20
|\ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into rurik.mysql.com:/home/igor/dev/mysql-5.0-0
| * | | | | | | | | | | Fixed bug #17164.igor@rurik.mysql.com2006-03-241-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If the WHERE condition of a query contained an ORed FALSE term then the set of tables whose rows cannot serve for null complements in outer joins was determined incorrectly. It resulted in blocking possible conversions of outer joins into joins for such queries.
* | | | | | | | | | | | Merge bk-internal.mysql.com:/home/bk/mysql-5.0dlenev@mysql.com2006-03-242-0/+75
|\ \ \ \ \ \ \ \ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | into mysql.com:/home/dlenev/mysql-5.0-bg18153
View Lorry Controller Status