An error occurred fetching the project authors.
- 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.
-
- 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).
-
- 30 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
open cursor after mysql_stmt_execute" + post-review fixes. The bug was caused by wrong flags in stmt->server_status on the client side: if there was no cursor, the server didn't send server_status flags to the client, and the old flags were used to set up the fetch function of a statement. Consequently, stmt_read_row_from_cursor was used when there was no cursor. The fix fixes the server to always send server flags to the client.
-
- 28 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
CURSOR_TYPE_READ_ONLY select within select". The bug was caused by the reset of thd->mem_root to thd->main_mem_root in Item_subselect::exec, which in turn triggered too early free_root() for data which was needed on subsequent fetches from a cursor. This reset also caused a memory leak in stored procedures, as subsequent executions of instructions containing a subselect were allocating memory in thd->main_mem_root, which is not freed until the end of the entire SP, instead of the per-call mem_root, which is freed in the end of execution of the instruction.
-
- 24 Jun, 2005 1 commit
-
-
jimw@mysql.com authored
it can use it to switch to only quoting apostrophes by doubling them when it is in effect. (Bug #10214)
-
- 20 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
-
- 19 Jun, 2005 2 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
use tabs.
-
- 17 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
-
- 14 Jun, 2005 2 commits
-
-
bell@sanja.is.com.ua authored
-
evgen@moonbone.local authored
Wrong method for creating temporary field was choosen, which results in sending int field with int header but lonlong data. Test case is added to mysql_client_test.c because client library is required to test the bug.
-
- 09 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
CURSOR_TYPE_READ_ONLY". The bug was that we (me) don't perform proper cleanups of the prepared statement when done fetching from a cursor. Another patch.
-
- 01 Jun, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 27 May, 2005 1 commit
-
-
gluh@eagle.intranet.mysql.r18.ru authored
set net->no_send_error to 0 before execution of each element of multiquery statement to provide the sending of error to client
-
- 18 May, 2005 1 commit
-
-
monty@mysql.com authored
This makes it easier to give an error in the handler if there was a problem generating an auto-increment value
-