summaryrefslogtreecommitdiff
path: root/tests
Commit message (Collapse)AuthorAgeFilesLines
* Merge mysql.com:/home/dlenev/src/mysql-5.0-mergesdlenev@mysql.com2005-12-121-0/+35
|\ | | | | | | into mysql.com:/home/dlenev/src/mysql-5.1-merges
| * Fix value returned by mysql_warning_count() after fetching a preparedjimw@mysql.com2005-12-061-0/+35
| | | | | | | | statement that generated a warning. (Bug #15510)
* | Bug#10932 - Building server with key limit of 128, makes test cases failingo@mysql.com2005-12-021-1/+1
|/ | | | | | | | | | | | | | | | Allow for configuration of the maximum number of indexes per table. Added and used a configure.in macro. Replaced fixed limits by the configurable limit. Limited MyISAM indexes to its hard limit. Fixed a bug in opt_range.cc for many indexes with InnoDB. Tested for 2, 63, 64, 65, 127, 128, 129, 255, 256, and 257 indexes. Testing this part of the bugfix requires rebuilding of the server with different options. This cannot be done with our test suite. Therefore I added the necessary test files to the bug report. If you repeat the tests, please note that the ps_* tests fail for everything but 64 indexes. This is because of differences in the meta data, namely field lengths for index names etc.
* A test case for Bug#14845 "mysql_stmt_fetch returns MYSQL_NO_DATAkonstantin@mysql.com2005-11-181-0/+44
| | | | when COUNT(*) is 0". The bug itself cannot be repeated.
* A fix and a test case for Bug#13524 "lock timeout gives konstantin@mysql.com2005-11-171-1/+62
| | | | incorrect warning on open cursor"
* A fix and a test case for Bug#13488 "Left outer join query incorrectlykonstantin@mysql.com2005-11-091-0/+69
| | | | gives MYSQL_DATA_TRUNCATED"
* A fix and a test case for Bug#14210 "Simple query with > operator on konstantin@mysql.com2005-11-031-0/+54
| | | | | | large table gives server crash": make sure that when a MyISAM temporary table is created for a cursor, it's created in its memory root, not the memory root of the current query.
* Merge ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-4.1jani@ua141d10.elisa.omakaista.fi2005-10-271-0/+19
|\ | | | | | | into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0-tmp
| * Merge mysql.com:/home/jimw/my/mysql-4.1-12925jimw@mysql.com2005-10-251-0/+19
| |\ | | | | | | | | | into mysql.com:/home/jimw/my/mysql-4.1-clean
| | * Fix incorrect casts in my_getopt code that capped the maximum of longlongjimw@mysql.com2005-10-251-0/+19
| | | | | | | | | | | | options to the wrong value. (Bug #12925)
| * | Bug #12698 abnormal program termination running mysql_client_testmsvensson@neptunus.(none)2005-10-131-92/+0
| | | | | | | | | | | | | | | - Move test for bug#93 from mysql_client_test.c to show_check.test - No need for test written in c
| * | Bug #12698 abnormal program termination running mysql_client_testmsvensson@neptunus.(none)2005-10-131-2/+1
| |/ | | | | | | | | | | | | - The testcase create a .frm file consisting of "junk". Unfortunately the "junk" wasn't written to the .frm file if mysql_client_test was run with -s option to make it run silent. This most likely caused the file never to be created on windows, and thus the test case failed.
| * Bug#12817 SHOW STATUS now blob fieldsgluh@eagle.intranet.mysql.r18.ru2005-09-091-3/+3
| | | | | | | | | | | | | | | | | | | | | | This fix is cancellation of ChangeSet 1.2329 05/07/12 08:35:30 reggie@linux.site +8 -0 Bug 7142 Show Fields from fails using Borland's dbExpress interface The reason is we can't fix bug#7142 without breaking of existing applications/APIs that worked fine with earlier 4.1 bug 7142 is fixed in 5.0
* | A fix and a test case for Bug#6513 "Test Suite: Values inserted by using konstantin@mysql.com2005-09-221-2/+5
| | | | | | | | | | | | | | | | | | | | cursor is interpreted latin1 character and Bug#9819 "Cursors: Mysql Server Crash while fetching from table with 5 million records." A fix for a possible memory leak when fetching into an SP cursor in a long loop. The patch uses a common implementation of cursors in the binary protocol and in stored procedures and implements materialized cursors. For implementation details, see comments in sql_cursor.cc
* | Merge mysql.com:/home/jimw/my/mysql-4.1-cleanjimw@mysql.com2005-08-311-2/+2
|\ \ | |/ | | | | into mysql.com:/home/jimw/my/mysql-5.0-clean
| * Fix incorrect spellings of "dropped" in source and tests. (Bug #12828)jimw@mysql.com2005-08-301-2/+2
| |
* | Merge ahristov@bk-internal.mysql.com:/home/bk/mysql-5.0andrey@lmy004.2005-08-271-0/+76
|\ \ | | | | | | | | | into lmy004.:/work/mysql-5.0-bug11904
| * | fix for bug #11904 (select statement, cursor, grouping wrong results)andrey@lmy004.2005-08-261-0/+76
| | |
* | | Merge bk-internal.mysql.com:/home/bk/mysql-5.0monty@mishka.local2005-08-251-0/+35
|\ \ \ | |/ / |/| | | | | into mishka.local:/home/my/mysql-5.0
| * | Merge mishka.local:/home/my/mysql-4.1monty@mishka.local2005-08-251-0/+35
| |\ \ | | |/ | | | | | | into mishka.local:/home/my/mysql-5.0
| | * Fix bug #11718 query with function, join and order by returns wrong type.evgen@moonbone.local2005-08-171-0/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | create_tmp_field_from_item() was creating tmp field without regard to original field type of Item. This results in wrong type being reported to client. To create_tmp_field_from_item() added special handling for Items with DATE/TIME field types to preserve their type.
* | | Merge mysql.com:/home/jimw/my/mysql-5.0-11680jimw@mysql.com2005-08-241-2/+1
|\ \ \ | |/ / |/| | | | | into mysql.com:/home/jimw/my/mysql-5.0-clean
| * | Fix build using --without-server. (Bug #11680)jimw@mysql.com2005-08-231-2/+1
| | |
* | | WL#2486 - natural and using join according to SQL:2003timour@mysql.com2005-08-231-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Provide backwards compatibility extension to name resolution of coalesced columns. The patch allows such columns to be qualified with a table (and db) name, as it is in 4.1. Based on a patch from Monty. * Adjusted tests accordingly to test both backwards compatible name resolution of qualified columns, and ANSI-style resolution of non-qualified columns. For this, each affected test has two versions - one with qualified columns, and one without.
* | | Merge bk-internal.mysql.com:/home/bk/mysql-5.0monty@mysql.com2005-08-151-2/+2
|\ \ \ | | | | | | | | | | | | into mysql.com:/home/my/mysql-5.0
| * \ \ Merge mysql.com:/home/timka/mysql/src/5.0-virgintimour@mysql.com2005-08-121-2/+2
| |\ \ \ | | | | | | | | | | | | | | | into mysql.com:/home/timka/mysql/src/5.0-2486-merge
| | * | | Implementation of WL#2486 -timour@mysql.com2005-08-121-2/+2
| | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "Process NATURAL and USING joins according to SQL:2003". * Some of the main problems fixed by the patch: - in "select *" queries the * expanded correctly according to ANSI for arbitrary natural/using joins - natural/using joins are correctly transformed into JOIN ... ON for any number/nesting of the joins. - column references are correctly resolved against natural joins of any nesting and combined with arbitrary other joins. * This patch also contains a fix for name resolution of items inside the ON condition of JOIN ... ON - in this case items must be resolved only against the JOIN operands. To support such 'local' name resolution, the patch introduces a stack of name resolution contexts used at parse time. NOTICE: - This patch is not complete in the sense that - there are 2 test cases that still do not pass - one in join.test, one in select.test. Both are marked with a comment "TODO: WL#2486". - it does not include a new test specific for the task
* | | | Save and clear run context before executing a stored function or trigger and ↵monty@mysql.com2005-08-151-1/+1
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | restore it afterwards. This allows us to use statement replication with functions and triggers The following things are fixed with this patch: - NOW() and automatic timestamps takes the value from the main event for functions and triggers (which allows these to replicate with statement level logging) - No side effects for triggers or functions with auto-increment values(), last_insert_id(), rand() or found_rows() - Triggers can't return result sets Fixes bugs: #12480: NOW() is not constant in a trigger #12481: Using NOW() in a stored function breaks statement based replication #12482: Triggers has side effects with auto_increment values #11587: trigger causes lost connection error
* | | Merge xiphis.org:/usr/home/antony/work2/mysql-4.1acurtis@xiphis.org2005-08-111-1/+1
|\ \ \ | | |/ | |/| | | | into xiphis.org:/usr/home/antony/work2/merge-5.0
| * | Fixed compiler warningsmonty@mysql.com2005-07-281-2/+3
| | |
* | | A fix and a test case for Bug#12243 "MySQL Server crashes with 2 konstantin@mysql.com2005-08-101-0/+61
| | | | | | | | | | | | | | | cursors (+ commit)" and Bug#11832 "Server crash with InnoDB + Cursors" See comments to the changed files.
* | | Fix coding style.konstantin@mysql.com2005-08-101-10/+16
| | |
* | | A fix for Bug#11901 "mysql_stmt_attr_set CURSOR_TYPE_READ_ONLY join inkonstantin@mysql.com2005-08-101-0/+123
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | subqry order by server crash": failing DBUG_ASSERT(curr_join == this) when opening a cursor. Ensure that for top-level join curr_join == join (always), and thus fix the failing assert. curr_join is a hack to ensure that uncacheable subqueries can be re-evaluated safely, and should be never different from main join in case of top-level join.
* | | A fix and a test case for Bug#11909 "mysql_stmt_attr_set konstantin@mysql.com2005-08-081-0/+120
| |/ |/| | | | | CURSOR_TYPE_READ_ONLY nested queries corrupt result"
* | Merge mronstrom@bk-internal.mysql.com:/home/bk/mysql-4.1pappa@c-450ae253.1238-1-64736c10.cust.bredbandsbolaget.se2005-07-211-0/+45
|\ \ | |/ | | | | into c-450ae253.1238-1-64736c10.cust.bredbandsbolaget.se:/home/pappa/mysql-5.0
| * Merge grichter@bk-internal.mysql.com:/home/bk/mysql-4.1georg@lmy002.wdf.sap.corp2005-07-201-0/+44
| |\ | | | | | | | | | into lmy002.wdf.sap.corp:/home/georg/work/mysql/prod/mysql-4.1
| | * cs fixes from last commit georg@lmy002.wdf.sap.corp2005-07-201-10/+10
| | |
| | * fix for bug#12001georg@lmy002.wdf.sap.corp2005-07-191-0/+44
| | |
* | | Implement MySQL framework to support consistent read views inkonstantin@mysql.com2005-07-201-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | cursors. This should fix Bug#11813 when InnoDB part is in (tested with a draft patch). The idea of the patch is that if a storage engine supports consistent read views, we open one when open a cursor, set is as the active view when fetch from the cursor, and close together with cursor close.
* | | Merge bk-internal:/home/bk/mysql-5.0jimw@mysql.com2005-07-191-11/+19
|\ \ \ | | | | | | | | | | | | into mysql.com:/home/jimw/my/mysql-5.0-clean
| * | | Cleanups after merge from 4.1.jimw@mysql.com2005-07-191-14/+22
| | | |
| * | | Merge mysql.com:/home/jimw/my/mysql-4.1-cleanjimw@mysql.com2005-07-191-3/+3
| |\ \ \ | | |/ / | | | | | | | | into mysql.com:/home/jimw/my/mysql-5.0-clean
| | * | Merge rburnett@bk-internal.mysql.com:/home/bk/mysql-4.1reggie@linux.site2005-07-181-3/+3
| | |\ \ | | | |/ | | |/| | | | | into linux.site:/home/reggie/bk/bug7142
| | | * Bug #7142 Show Fields from fails using Borland's dbExpress interfacereggie@linux.site2005-07-121-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The problem here is that columns that have an especially long type such as an enum type with many options would be longer than 40 chars but the type column returned from show columns always was defined as varchar(40). This is fixed in 5.0 using info schema.
| | * | Merge tulin@bk-internal.mysql.com:/home/bk/mysql-4.1tomas@poseidon.ndb.mysql.com2005-07-151-4/+14
| | |\ \ | | | | | | | | | | | | | | | into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1-new
| | | * | fix for #11808 backported.ramil@mysql.com2005-07-141-4/+14
| | | |/
* | | | A fix and a test case for Bug#10760 and complementary cleanups. konstantin@mysql.com2005-07-191-0/+129
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The idea of the patch is that every cursor gets its own lock id for table level locking. Thus cursors are protected from updates performed within the same connection. Additionally a list of transient (must be closed at commit) cursors is maintained and all transient cursors are closed when necessary. Lastly, this patch adds support for deadlock timeouts to TLL locking when using cursors. + post-review fixes.
* | | Merge bk-internal.mysql.com:/home/bk/mysql-5.0monty@mishka.local2005-07-181-71/+71
|\ \ \ | | | | | | | | | | | | into mishka.local:/home/my/mysql-5.0
| * | | Cleanups during reviewmonty@mishka.local2005-07-181-71/+71
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changed defaults option --instance to --defaults-group-suffix Changed option handling to allow --defaults-file, --defaults-extra-file and --defaults-group-suffix to be given in any order Changed MYSQL_INSTANCE to MYSQL_GROUP_SUFFIX mysql_print_defaults now understands --defaults-group-suffix Remove usage of my_tempnam() (not safe function) if( -> if ( and while( to while (
* | | | cs fixesgeorg@lmy002.wdf.sap.corp2005-07-161-6/+6
| | | |
View Lorry Controller Status