An error occurred fetching the project authors.
- 14 Sep, 2005 1 commit
-
-
dlenev@mysql.com authored
This bug occurs when some trigger for table used by DML statement is created or changed while statement was waiting in lock_tables(). In this situation prelocking set which we have calculated becames invalid which can easily lead to errors and even in some cases to crashes. With proposed patch we no longer silently reopen tables in lock_tables(), instead caller of lock_tables() becomes responsible for reopening tables and recalculation of prelocking set.
-
- 13 Sep, 2005 2 commits
-
-
gluh@eagle.intranet.mysql.r18.ru authored
Information_schema DB Bug#9846 Inappropriate error displayed while dropping table from 'INFORMATION_SCHEMA' Bug#10734 Grant of privileges other than 'select' and 'create view' should fail on schema Bug#10708 SP's can use INFORMATION_SCHEMA as ROUTINE_SCHEMA cumulative fix for bugs above(after review, 2nd version) added privilege check for information schema db & tables
-
kent@mysql.com authored
VC6 can't handle initializing const in declaration
-
- 02 Sep, 2005 2 commits
-
-
konstantin@mysql.com authored
The idea of the patch is to separate statement processing logic, such as parsing, validation of the parsed tree, execution and cleanup, from global query processing logic, such as logging, resetting priorities of a thread, resetting stored procedure cache, resetting thread count of errors and warnings. This makes PREPARE and EXECUTE behave similarly to the rest of SQL statements and allows their use in stored procedures. This patch contains a change in behaviour: until recently for each SQL prepared statement command, 2 queries were written to the general log, e.g. [Query] prepare stmt from @stmt_text; [Prepare] select * from t1 <-- contents of @stmt_text The chagne was necessary to prevent [Prepare] commands from being written to the general log when executing a stored procedure with Dynamic SQL. We should consider whether the old behavior is preferrable and probably restore it. This patch refixes Bug#7115, Bug#10975 (partially), Bug#10605 (various bugs in Dynamic SQL reported before it was disabled).
-
konstantin@mysql.com authored
- current_arena to stmt_arena: the thread may have more than one 'current' arenas: one for runtime data, and one for the parsed tree of a statement. Only one of them is active at any moment. - set_item_arena -> set_query_arena, because Item_arena was renamed to Query_arena a while ago - set_n_backup_item_arena -> set_n_backup_active_arena; the active arena is the arena thd->mem_root and thd->free_list are currently pointing at. - restore_backup_item_arena -> restore_active_arena (with the same rationale) - change_arena_if_needed -> activate_stmt_arena_if_needed; this method sets thd->stmt_arena active if it's not done yet.
-
- 19 Aug, 2005 1 commit
-
-
elliot@mysql.com authored
-
- 17 Aug, 2005 1 commit
-
-
elliot@mysql.com authored
In cp932, '\' character can be the second byte in a multi-byte character stream. This makes it difficult to use mysql_escape_string. Added flag to indicate which languages allow '\' as second byte of multibyte sequence so that when putting a prepared statement into the binlog we can decide at runtime whether hex encoding is really needed.
-
- 10 Aug, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 09 Aug, 2005 1 commit
-
-
dlenev@mysql.com authored
cause crash on update". Let us update "thd" pointer in LEX, all its units and in LEX::result before executing statement in trigger body, since triggers are associated with TABLE object and because of this can be used in different threads.
-
- 08 Aug, 2005 3 commits
-
-
sergefp@mysql.com authored
* Cleanup SP Cache code, now SP Cache only deletes sp_head objects in sp_cache_flush_obsolete() invalidates all pointers to routines in the cache. * Use new SP Cache use contract in the code. There is no test case because it doesn't seem to be possible to cause thread races to end the same way they end in heavy-load test. This patch removes the crash in heavy test.
-
konstantin@mysql.com authored
CURSOR_TYPE_READ_ONLY nested queries corrupt result"
-
dlenev@mysql.com authored
result set". To enable full access to contents of I_S tables from stored functions or statements that use them, we manipulate with thread's open tables state and ensure that we won't cause deadlock when we open tables by ignoring flushes and name-locks. Building of contents of I_S.TABLES no longer requires locking of tables since we use use handler::info() method with HA_STATUS_AUTO flag instead of handler::update_auto_increment() for obtaining information about auto-increment values. But this also means that handlers have to implement support for HA_STATUS_AUTO flag (particularly InnoDB needs it).
-
- 29 Jul, 2005 1 commit
-
-
monty@mysql.com authored
Before the fix in ~Prepared_statments we got a memory leak when executing mysql_client_test.test Note that test 'variables.test' fails. This will be fixed when Jimw pushes the fix for Bug 10351
-
- 27 Jul, 2005 1 commit
-
-
georg@lmy002.wdf.sap.corp authored
Query has to be written to the log before calling thd->set_statement(&stmt_backup), otherwise query will be empty. Setting thd->enabe_slow_log to FALSE prevents that dispatch_command logs the (empty) query again.
-
- 19 Jul, 2005 2 commits
-
-
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.
-
monty@mishka.local 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 (
-
- 15 Jul, 2005 1 commit
-
-
ramil@mysql.com authored
Fix handling of floats and doubles when using prepared statements API in the embedded server.
-
- 14 Jul, 2005 1 commit
-
-
konstantin@mysql.com authored
in cursors.
-
- 13 Jul, 2005 1 commit
-
-
konstantin@mysql.com authored
data": remove the fix for another bug (8807) that added OUTER_REF_TABLE_BIT to all subqueries that used a placeholder to prevent their evaluation at prepare. As this bit hanged in Item_subselect::used_tables_cache for ever, a constant subquery with a placeholder was never evaluated as such, which caused wrong choice of the execution plan for the statement. - to fix Bug#8807 backport a better fix from 5.0 - post-review fixes.
-
- 04 Jul, 2005 1 commit
-
-
monty@mysql.com authored
Better fix for ON DUPLICATE KEY UPDATE
-
- 01 Jul, 2005 4 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
-
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).
-
bell@sanja.is.com.ua authored
-
- 27 Jun, 2005 1 commit
-
-
monty@mishka.local authored
#9728 'Decreased functionality in "on duplicate key update #8147 'a column proclaimed ambigous in INSERT ... SELECT .. ON DUPLICATE' This ensures fields are uniquely qualified and also that one can't update other tables in the ON DUPLICATE KEY UPDATE part
-
- 23 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
We need every instruction to have its own arena, because we want to track instruction's state (INITIALIZED_FOR_SP -> EXECUTED). Because of `if' statements and other conditional instructions used in stored procedures, not every instruction of a stored procedure gets executed during the first (or even subsequent) execution of the procedure. So it's better if we track the execution state of every instruction independently. All instructions of a given procedure now also share sp_head's mem_root, but keep their own free_list. This simplifies juggling with free Item lists in sp_head::execute. - free_items() moved to be a member of Query_arena. - logic of 'backup_arena' debug member of Query_arena has been changed to support multi-backups. Until now, TRUE 'backup_arena' meant that there is exactly one active backup of the THD arena. Now it means simply that the arena is used for backup, so that we can't accidentally overwrite an existing backup. This allows doing multiple backups, e.g. in sp_head::execute and Cursor::fetch, when THD arena is already backed up but we want to set yet another arena (usually the 'permanent' arena, to save permanent transformations/optimizations of a parsed tree).
-
- 22 Jun, 2005 2 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
main_mem_root is moved out of class Query_arena.
-
- 20 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
-
- 17 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
-
- 16 Jun, 2005 2 commits
-
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
Bug#8367 "low log doesn't gives complete information about prepared statements" Implement status variables for prepared statements commands (a port of the patch by Andrey Hristov). See details in comments to the changed files. No test case as there is no way to test slow log/general log in mysqltest.
-
- 15 Jun, 2005 1 commit
-
-
serg@serg.mylan authored
Item_buff -> Cached_item Item_arena -> Query_arena TEST_ASSERT -> YYERROR_UNLESS
-
- 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.
-
- 08 Jun, 2005 3 commits
-
-
dlenev@brandersnatch.localdomain authored
In order to make multi-delete SP friendly we need to have all table locks for the elements of main statement table list properly set at the end of parsing. Also performed small cleanup: We don't need relink_tables_for_multidelete() any longer since the only case now when TABLE_LIST::correspondent_table is non-zero are tables in auxilary table list of multi-delete and these tables are handled specially in mysql_multi_delete_prepare().
-
konstantin@mysql.com authored
-
konstantin@mysql.com authored
-
- 07 Jun, 2005 1 commit
-
-
konstantin@mysql.com authored
don't evaluate subqueries during statement prepare, even if they are not correlated. With post-review fixes.
-
- 16 May, 2005 1 commit
-
-
monty@mysql.com authored
Fixed bug in mysql_stmt_fetch() when retrieving rows to return
-