An error occurred fetching the project authors.
- 30 Jul, 2005 1 commit
-
-
sergefp@mysql.com authored
its body, but lets each statement to get/release its own locks. This allows a broader set of statements to be executed inside PROCEDUREs (but breaks replication) This patch should fix BUG#8072, BUG#8766, BUG#9563, BUG#11126
-
- 28 Jul, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
other sql_mode fixes
-
- 09 Jul, 2005 1 commit
-
-
dlenev@mysql.com authored
crash if referencing a table" and several other related bugs. Fix for bug #11834 "Re-execution of prepared statement with dropped function crashes server." which was spotted during work on previous bugs. Also couple of nice cleanups: - Replaced two separate hashes for stored routines used by statement with one. - Now instead of doing one pass through all routines used in statement for caching them and then doing another pass for adding their tables to table list, we do only one pass during which do both things.
-
- 01 Jul, 2005 3 commits
-
-
bell@sanja.is.com.ua authored
-
dlenev@brandersnatch.localdomain authored
"Stored procedures: crash with function calling itself". Disallow recursive stored routines until we either make Item's and LEX reentrant safe or will use spearate sp_head instances (and thus separate LEX objects and Item trees) for each routine invocation.
-
bell@sanja.is.com.ua authored
-
- 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 1 commit
-
-
konstantin@mysql.com authored
main_mem_root is moved out of class Query_arena.
-
- 15 Jun, 2005 1 commit
-
-
serg@serg.mylan authored
Item_buff -> Cached_item Item_arena -> Query_arena TEST_ASSERT -> YYERROR_UNLESS
-
- 14 Jun, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 27 May, 2005 2 commits
-
-
dlenev@brandersnatch.localdomain authored
We can't have Item_trigger_field as aggregated object inside of sp_instr_set_trigger_field class since in this case its destructor will be called twice. So instead let us create this Item separately and store pointer to it in instruction object.
-
msvensson@neptunus.(none) authored
-
- 04 Mar, 2005 2 commits
-
-
acurtis@pcgem.rdg.cyberkinetica.com authored
Crashes with stored procedure return non-string values Also fixes Bug#2773
-
dlenev@brandersnatch.localdomain authored
and some SP-related cleanups. - We don't have separate stage for calculation of list of tables to be prelocked and doing implicit LOCK/UNLOCK any more. Instead we calculate this list at open_tables() and do implicit LOCK in lock_tables() (and UNLOCK in close_thread_tables()). Also now we support cases when same table (with same alias) is used several times in the same query in SP. - Cleaned up execution of SP. Moved all common code which handles LEX and does preparations before statement execution or complex expression evaluation to auxilary sp_lex_keeper class. Now all statements in SP (and corresponding instructions) that evaluate expression which can contain subquery have their own LEX.
-
- 08 Feb, 2005 1 commit
-
-
pem@mysql.comhem.se authored
Collect all tables and SPs refered by a statement, and open all tables with an implicit LOCK TABLES. Do find things refered by triggers and views, we open them first (and then repeat this until nothing new is found), before doing the actual lock tables.
-
- 24 Nov, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
out of order". (final version) Now instead of binding Item_trigger_field to TABLE objects during trigger definition parsing at table open, we perform pass through special list of all such objects in trigger. This allows easily check all references to fields in old/new version of row in trigger during execution of CREATE TRIGGER statement (this is more courtesy for users since we can't check everything anyway). We also report that such reference is bad by returning error from Item_trigger_field::fix_fields() method (instead of setup_field()) This means that if trigger is broken we will bark during trigger execution instead of trigger definition parsing at table open. (i.e. now we allow to open tables with broken triggers).
-
- 09 Nov, 2004 1 commit
-
-
monty@mysql.com authored
Added push_back(void *, MEM_ROOT *) to make some list-handling code easier that needs to be allocated in a different mem-root (Before one had to change thd->mem_root ; push_back(); restore mem_root.
-
- 17 Sep, 2004 1 commit
-
-
pem@mysql.comhem.se authored
-
- 10 Sep, 2004 1 commit
-
-
pem@mysql.comhem.se authored
Dropping the table was not the real problem, the problem was with errors occuring within error handlers.
-
- 08 Sep, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
After review and after merge fixes.
-
- 07 Sep, 2004 1 commit
-
-
dlenev@brandersnatch.localdomain authored
Mostly needed for Monty for him getting notion what needed for triggers from new .FRM format. Things to be done: - Right placement of trigger's invocations - Right handling of errors in triggers (including transaction rollback) - Support for priviliges - Right handling of DROP/RENAME table (hope that it will be handled automatically with merging of .TRG into .FRM file) - Saving/restoring some information critical for trigger creation and replication with their definitions (e.g. sql_mode, creator, ...) - Replication Already has some known bugs so probably not for general review.
-
- 26 Aug, 2004 1 commit
-
-
pem@mysql.comhem.se authored
This finishes (almost) WL#2002: Implement stored procedure GOTO. Only the syntax issue for free labels remains ("label L;" vs "L:").
-
- 24 Aug, 2004 1 commit
-
-
pem@mysql.comhem.se authored
and BUG#336: Subselects with tables does not work as values for local SP variables (which was closed before with a temp. fix, but not actually fixed).
-
- 17 Aug, 2004 1 commit
-
-
pem@mysql.comhem.se authored
Mostly done, it works, but the temporary LABEL syntax still to be fixed.
-
- 06 Aug, 2004 1 commit
-
-
pem@mysql.comhem.se authored
and tried to do it properly this time, digging out all show commands that need the multi results flag set.
-
- 02 Aug, 2004 1 commit
-
-
pem@mysql.comhem.se authored
Added a simple optimizer that shortcuts jumps and skip unused instructions.
-
- 09 Jun, 2004 1 commit
-
-
pem@mysql.comhem.se authored
It's not possible to quote the definition according to the current sql_mode setting, so instead we use the setting stored with the SP (that's how it's parsed anyway), and show this setting in the SHOW CREATE output.
-
- 26 May, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 19 May, 2004 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 06 Apr, 2004 1 commit
-
-
pem@mysql.comhem.se authored
Complex return types were not stored correctly in the mysql.proc table.
-
- 05 Apr, 2004 1 commit
-
-
pem@mysql.comhem.se authored
Backpatching overwrote already backpatched instructions, which made it skip the hpop instruction; possibly not only a problem for handlers, but this is one known case when it happened.
-
- 29 Mar, 2004 1 commit
-
-
pem@mysql.comhem.se authored
Added new test cases for this, and adjusted old tests accordingly, and new error codes and messages. Fixed bugs in some tests (bug2673 and use test). Added debug printing of instructions in SPs.
-
- 11 Mar, 2004 1 commit
-
-
pem@mysql.comhem.se authored
Phase 2: Make SPs belong to a DB, and use qualified names. As a side effect, using USE in an SP is no longer allowed. (It just doesn't work otherwise.)
-
- 17 Feb, 2004 1 commit
-
-
pem@mysql.comhem.se authored
Phase 1: Introduced sp_name class, for qualified name support.
-
- 16 Dec, 2003 1 commit
-
-
pem@mysql.comhem.se authored
Added missing cleanup in sp-security.test.
-
- 15 Dec, 2003 1 commit
-
-
pem@mysql.comhem.se authored
-
- 13 Dec, 2003 1 commit
-
-
pem@mysql.comhem.se authored
(Also put the hostpart back in the definer column.)
-
- 12 Dec, 2003 1 commit
-
-
pem@mysql.comhem.se authored
make characteristics (and SHOW) work right, we had to separate the old definition blob in the mysql.proc table into separate fields for parameters, return type, and body, and handle the characteristics (like SQL SECURITY) separately... and then reassemble the CREATE string for parsing, of course. This is rather ugly, mostly the parser bit. (Hopefully that will be better with the new parser.)
-
- 10 Dec, 2003 1 commit
-
-
pem@mysql.comhem.se authored
Also made the parsing and handling of SP characteristics more general and extendable, and added a few ch:istics.
-
- 17 Nov, 2003 1 commit
-
-
gluh@gluh.mysql.r18.ru authored
WL#1263: Support for the attributes COMMENT and SUID in CREATE/ALTER PROCEDURE/FUNCTION
-