An error occurred fetching the project authors.
- 10 Nov, 2005 1 commit
-
-
anozdrin@mysql.com authored
checks on trigger activation)
-
- 06 Nov, 2005 1 commit
-
-
igor@rurik.mysql.com authored
-
- 03 Nov, 2005 1 commit
-
-
igor@rurik.mysql.com authored
-
- 02 Nov, 2005 1 commit
-
-
igor@rurik.mysql.com authored
new file sql_table.cc, handler.h: Fixed bug #14540. Added error mnemonic code HA_ADMIN_NOT_BASE_TABLE to report that an operation cannot be applied for views. view.test, view.result: Added a test case for bug #14540. errmsg.txt: Fixed bug #14540. Added error ER_CHECK_NOT_BASE_TABLE.
-
- 27 Oct, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 11 Oct, 2005 1 commit
-
-
pem@mysql.com authored
Disallow conflicting use of variables named "password" and "names". If such a variable is declared, and "SET ... = ..." is used for them, an error is returned; the user must resolve the conflict by either using `var` (indicating that the local variable is set) or by renaming the variable. This is necessary since setting "password" and "names" are treated as special cases by the parser.
-
- 05 Oct, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 30 Sep, 2005 1 commit
-
-
serg@serg.mylan authored
-
- 23 Sep, 2005 1 commit
-
-
osku@127.(none) authored
-
- 16 Sep, 2005 1 commit
-
-
georg@lmy002.wdf.sap.corp authored
-
- 14 Sep, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
view definer information syntax/storage/replication fixed SOURCE field of .frm
-
- 13 Sep, 2005 1 commit
-
-
pem@mysql.com authored
Second version after review. Allow 'set autocommit' in procedures, but not functions or triggers. Can return error in run-time (when a function calls a procedure).
-
- 04 Sep, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 02 Sep, 2005 1 commit
-
-
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).
-
- 18 Aug, 2005 2 commits
-
-
dlenev@mysql.com authored
If we are in stored function or trigger we should ensure that we won't change table that is already used by calling statement (this can damage table or easily cause infinite loops). Particularly this means that recursive triggers should be disallowed.
-
igor@rurik.mysql.com authored
Added a test case for bug #10970. view.result: Added a test case for bug #10970. Modified the error messages for error ER_VIEW_SELECT_TMPTABLE. sql_view.cc: Fixed bug #10970. In the function mysql_create_view if a view does not refer any tables directly the variable table must be updated after the call of open_and_lock_tables. errmsg.txt: Modified the error messages for error ER_VIEW_SELECT_TMPTABLE (when fixing bug #10970).
-
- 15 Aug, 2005 1 commit
-
-
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
-
- 12 Aug, 2005 1 commit
-
-
serg@sergbook.mysql.com authored
Now we keep all active XID's in a hash
-
- 10 Aug, 2005 1 commit
-
-
dlenev@mysql.com authored
We should not allow FLUSH statement to be executed inside both triggers and stored functions.
-
- 07 Aug, 2005 1 commit
-
-
ingo@mysql.com authored
Give the user a warning if he tries to destroy the default key cache.
-
- 06 Aug, 2005 1 commit
-
-
jimw@mysql.com authored
width beyond the maximum. (Bug #6080)
-
- 02 Aug, 2005 2 commits
-
-
jimw@mysql.com authored
that is outside the acceptable date range. (Bug #10627)
-
bell@sanja.is.com.ua authored
frequently used command sequence replaced with inline function
-
- 27 Jul, 2005 1 commit
-
-
jimw@mysql.com authored
produce a sensible error when that limit is exceeded. (Bug #11602)
-
- 22 Jul, 2005 1 commit
-
-
paul@snake-hub.snake.net authored
Change an ` quote to ' (' is used everywhere else) This does not affect any test results.
-
- 19 Jul, 2005 1 commit
-
-
dlenev@mysql.com authored
"Triggers have the wrong namespace" "Triggers: duplicate names allowed" "Triggers: CREATE TRIGGER does not accept fully qualified names" "SHOW TRIGGERS"
-
- 17 Jul, 2005 1 commit
-
-
patg@radha.local authored
WHERE statement"
-
- 16 Jul, 2005 1 commit
-
-
patg@krsna.patg.net authored
deallocation cleanup
-
- 13 Jul, 2005 1 commit
-
-
dlenev@mysql.com authored
of stored routines definitions even if we already have some tables open and locked. To avoid deadlocks in this case we have to put certain restrictions on locking of mysql.proc table. This allows to use stored routines safely under LOCK TABLES without explicitly mentioning mysql.proc in the list of locked tables. It also fixes bug #11554 "Server crashes on statement indirectly using non-cached function".
-
- 07 Jul, 2005 1 commit
-
-
hf@deer.(none) authored
-
- 01 Jul, 2005 2 commits
-
-
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
-
- 22 Jun, 2005 1 commit
-
-
jimw@mysql.com authored
to include how much stack space we need. (Bug #11213)
-
- 20 Jun, 2005 2 commits
-
-
konstantin@mysql.com authored
-
msvensson@neptunus.(none) authored
- Print warning that says display width is not supported for datatype TIMESTAMP, if user tries to create a TIMESTAMP column with display width. - Use display width for TIMESTAMP only in type_timestamp test to make sure warning is displayed correctly.
-
- 19 Jun, 2005 1 commit
-
-
gbichot@quadita2.mysql.com authored
-
- 07 Jun, 2005 1 commit
-
-
dlenev@brandersnatch.localdomain authored
We should not allow explicit or implicit transaction commits inside of stored functions or triggers (so in autocommit mode we should not do commits after execution of sub-statement). Also since we don't support nested statement transactions in 5.0, we shouldn't commit or rollback stmt transactions while we are inside stored functions or triggers. This should be fixed in later (>=5.1) releases.
-
- 12 May, 2005 1 commit
-
-
konstantin@mysql.com authored
(crash on attempt to re-execute a statement with an open cursor) + post-review fixes.
-
- 05 May, 2005 1 commit
-
-
gbichot@quadita2.mysql.com authored
Approximative fixes for BUG#2610,2611,9100 i.e. WL#2146 binlogging/replication of routines (stored procs and functions). Approximative, because it's using our binlogging way (what we call "query"-level) and this is not as good as record-level binlog (5.1) would be. It imposes several limitations to routines, and has caveats (which I'll document, and for which the server will try to issue errors but that is not always possible). Reason I don't propagate caller info to the binlog as planned is that on master and slave users may be different; even with that some caveats would remain.
-
- 29 Apr, 2005 1 commit
-
-
hf@deer.(none) authored
-