An error occurred fetching the project authors.
- 14 Sep, 2005 3 commits
-
-
elliot@mysql.com authored
Fixed by making CREATE/ALTER/DROP PROCEDURE cause implicit commit.
-
bell@sanja.is.com.ua authored
view definer information syntax/storage/replication fixed SOURCE field of .frm
-
gluh@eagle.intranet.mysql.r18.ru authored
-
- 13 Sep, 2005 1 commit
-
-
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
-
- 12 Sep, 2005 1 commit
-
-
timour@mysql.com authored
The problem was in that add_table_to_list was testing for duplicate tables in a list of tables that included the created view.
-
- 10 Sep, 2005 2 commits
-
-
lars@mysql.com authored
-
timour@mysql.com authored
The problem was that in the first production in rule 'join_table', that processes simple cross joins, the parser was processing the second join operand before the first one due to unspecified priorities of JOINs. As a result in the case of cross joins the parser constructed a tree with incorrect nesting: the expression "t1 join t2 join t3 on some_cond" was interpreted as "t1 join (t2 join t3 on some_cond)" instead of "(t1 join t2) join t3 on some_cond". Because of this incorrect nesting the method make_join_on_context picked an incorrect table as the first table of the name resolution context. The solution assignes correct priorities to the related production.
-
- 09 Sep, 2005 1 commit
-
-
konstantin@mysql.com authored
-
- 07 Sep, 2005 1 commit
-
-
sergefp@mysql.com authored
* Allocate thd->user_var_events elements on appropriate mem_root * If several SP statements are binlogged as a single statement, collect all user var accesses they make (grep for StoredRoutinesBinlogging for details)
-
- 05 Sep, 2005 1 commit
-
-
bar@mysql.com authored
bug#9948 changed client-charset behavior in 4.1.x libmysql, which issue BC prob after review fixes
-
- 03 Sep, 2005 1 commit
-
-
eric@mysql.com authored
Handle systems like default FC4 where 127.0.0.1 doesn't always map to 'localhost' first. (Bug #11822)
-
- 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.
-
- 01 Sep, 2005 3 commits
-
-
lars@mysql.com authored
-
dlenev@mysql.com authored
multi-threaded environment". To avoid deadlocks between several simultaneously run account management commands (particularly between FLUSH PRIVILEGES/SET PASSWORD and GRANT commands) we should always take table and internal locks during their execution in the same order. In other words we should first open and lock privilege tables and only then obtain acl_cache::lock/LOCK_grant locks.
-
msvensson@neptunus.(none) authored
- Make sure that mysqltest always uses ssl when connecting to the server. - Pass a i32-bit int variable as argument to FIONREAD ioctl.
-
- 31 Aug, 2005 2 commits
-
-
lars@mysql.com authored
rpl_replicate_do.result: New test case sql_parse.cc: All SET statements should be executed by slave thd rpl_replicate_do.test: New test case
-
bar@mysql.com authored
bug#9948 changed client-charset behavior in 4.1.x libmysql, which issue BC prob sql_parse.cc: mysqld.cc: Added --skip-client-character-set-handshake. When this option is activated, client side character set (which is sent in handshake) is ignored, and server side default-character-set value is used for character_set_client and character_set_results, thus reprodicing 4.0 behaviour.
-
- 30 Aug, 2005 1 commit
-
-
osku@127.(none) authored
-
- 29 Aug, 2005 2 commits
-
-
ingo@mysql.com authored
-
ingo@mysql.com authored
Supplied the default database name for ALTER TABLE ... RENAME for the new table instead of the old tables db like we do for other ALTERs.
-
- 26 Aug, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 25 Aug, 2005 1 commit
-
-
sergefp@mysql.com authored
"Interleaved SPs execution is now binlogged properly, "SELECT spfunc()" is binlogged too. The known remaining issue is binlogging/replication of "a routine is deleted while it is executed" scenario.
-
- 24 Aug, 2005 1 commit
-
-
dlenev@mysql.com authored
We should not assume that "thd" argument of reload_acl_and_cache() is non-zero. Failure to do so will cause server to crash when one sends SIGHUP to it.
-
- 23 Aug, 2005 1 commit
-
-
lars@mysql.com authored
-
- 21 Aug, 2005 1 commit
-
-
monty@mishka.local authored
-
- 20 Aug, 2005 1 commit
-
-
monty@mishka.local authored
Fixed new bug when running a SP without a default database
-
- 19 Aug, 2005 1 commit
-
-
timour@mysql.com authored
- Corrected problem with N-way nested natural joins in PS mode. - Code cleanup - More asserts to check consistency of name resolution contexts - Fixed potential memory leak of name resolution contexts
-
- 18 Aug, 2005 1 commit
-
-
monty@mysql.com authored
-
- 15 Aug, 2005 3 commits
-
-
monty@mysql.com authored
Fixed failing test
-
lars@mysql.com authored
-
monty@mysql.com authored
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
-
- 13 Aug, 2005 1 commit
-
-
tsmith@.mysql.com authored
Don't skip SET command even if --replicate-wild* says to. E.g., SET ONE_SHOT TIME_ZONE = 'XYZ' should be executed (BUG #12542)
-
- 12 Aug, 2005 4 commits
-
-
serg@sergbook.mysql.com authored
Now we keep all active XID's in a hash
-
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
-
monty@mysql.com authored
Removed duplicate usage of TMP_TABLE_FORCE_MYISAM by making 'options' longlong
-
jimw@mysql.com authored
database after failing to execute a stored procedure in an inaccessible database. (Bug #12318)
-
- 11 Aug, 2005 1 commit
-
-
monty@mysql.com authored
-
- 10 Aug, 2005 2 commits
-
-
sergefp@mysql.com authored
-
hf@deer.(none) authored
-