An error occurred fetching the project authors.
- 02 Dec, 2005 1 commit
-
-
ingo@mysql.com authored
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.
-
- 18 Nov, 2005 1 commit
-
-
konstantin@mysql.com authored
when COUNT(*) is 0". The bug itself cannot be repeated.
-
- 17 Nov, 2005 1 commit
-
-
konstantin@mysql.com authored
incorrect warning on open cursor"
-
- 09 Nov, 2005 1 commit
-
-
konstantin@mysql.com authored
gives MYSQL_DATA_TRUNCATED"
-
- 03 Nov, 2005 1 commit
-
-
konstantin@mysql.com authored
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.
-
- 25 Oct, 2005 1 commit
-
-
jimw@mysql.com authored
options to the wrong value. (Bug #12925)
-
- 13 Oct, 2005 2 commits
-
-
msvensson@neptunus.(none) authored
- Move test for bug#93 from mysql_client_test.c to show_check.test - No need for test written in c
-
msvensson@neptunus.(none) authored
- 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.
-
- 21 Sep, 2005 1 commit
-
-
konstantin@mysql.com authored
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
-
- 09 Sep, 2005 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
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
-
- 30 Aug, 2005 1 commit
-
-
jimw@mysql.com authored
-
- 26 Aug, 2005 1 commit
-
-
andrey@lmy004. authored
-
- 23 Aug, 2005 1 commit
-
-
timour@mysql.com authored
* 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.
-
- 17 Aug, 2005 1 commit
-
-
evgen@moonbone.local authored
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.
-
- 12 Aug, 2005 1 commit
-
-
timour@mysql.com authored
"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
-
- 10 Aug, 2005 3 commits
-
-
konstantin@mysql.com authored
cursors (+ commit)" and Bug#11832 "Server crash with InnoDB + Cursors" See comments to the changed files.
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
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.
-
- 08 Aug, 2005 1 commit
-
-
konstantin@mysql.com authored
CURSOR_TYPE_READ_ONLY nested queries corrupt result"
-
- 28 Jul, 2005 1 commit
-
-
monty@mysql.com authored
-
- 20 Jul, 2005 2 commits
-
-
konstantin@mysql.com authored
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.
-
georg@lmy002.wdf.sap.corp authored
-
- 19 Jul, 2005 3 commits
-
-
jimw@mysql.com authored
-
konstantin@mysql.com authored
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.
-
georg@lmy002.wdf.sap.corp authored
-
- 18 Jul, 2005 1 commit
-
-
monty@mishka.local authored
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 (
-
- 16 Jul, 2005 1 commit
-
-
georg@lmy002.wdf.sap.corp authored
-
- 15 Jul, 2005 2 commits
-
-
georg@lmy002.wdf.sap.corp authored
test_client_character_set
-
georg@lmy002.wdf.sap.corp authored
When all rows are fetched subsequent calls to mysql_stmt_fetch return now MYSQL_NO_DATA instead of errorcode 1.
-
- 14 Jul, 2005 4 commits
-
-
konstantin@mysql.com authored
information about error".
-
ramil@mysql.com authored
-
konstantin@mysql.com authored
in cursors.
-
konstantin@mysql.com 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).
-
- 13 Jul, 2005 2 commits
-
-
konstantin@mysql.com authored
-
ramil@mysql.com authored
-
- 12 Jul, 2005 3 commits
-
-
reggie@linux.site authored
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.
-
georg@lmy002.wdf.sap.corp authored
-
georg@lmy002.wdf.sap.corp authored
Added api function mysql_get_character_set_info which provides information about the current client character set.
-
- 01 Jul, 2005 2 commits
-
-
konstantin@mysql.com authored
Add a test case for Bug#11656 "Server crash with mysql_stmt_fetch (cursors)", the bug itself is no longer present.
-
konstantin@mysql.com authored
CURSOR_TYPE_READ_ONLY date/datetime filter server crash". The fix adds support for Item_change_list in cursors (proper rollback of the modified item tree).
-