An error occurred fetching the project authors.
- 05 May, 2005 2 commits
-
-
holyfoot@hf-ibm.(none) authored
-
dlenev@brandersnatch.localdomain authored
a stored procedure" (version 2). To handle updates and inserts into view in SP properly we should set lock types for tables of the view's main select when we are opening view for prelocking purproses.
-
- 28 Apr, 2005 1 commit
-
-
jimw@mysql.com authored
The bug appears to have already been fixed. (Bug #7293)
-
- 22 Apr, 2005 1 commit
-
-
pem@mysql.comhem.se authored
-
- 21 Apr, 2005 1 commit
-
-
acurtis@xiphis.org authored
Bug partially fixed by 9775/9102 work on SP function return.
-
- 20 Apr, 2005 2 commits
-
-
acurtis@xiphis.org authored
Fix bug and implement return type casting.
-
pem@mysql.comhem.se authored
Bug in the optimizer caused an infinite loop for weird code.
-
- 19 Apr, 2005 2 commits
-
-
acurtis@xiphis.org authored
bugfix 9102 corrected the crashing, this corrects the result.
-
acurtis@xiphis.org authored
Initialization of fields for sp return type was not complete.
-
- 15 Apr, 2005 1 commit
-
-
pem@mysql.comhem.se authored
... actually, it was a query cache problem. (It shouldn't cache such queries)
-
- 14 Apr, 2005 1 commit
-
-
pem@mysql.comhem.se authored
overwrites IN variable and added error checking of variables for [IN]OUT parameters while rewriting the out parameter handling.
-
- 13 Apr, 2005 3 commits
-
-
pem@mysql.comhem.se authored
causes system crash.
-
pem@mysql.comhem.se authored
-
pem@mysql.comhem.se authored
-
- 12 Apr, 2005 1 commit
-
-
pem@mysql.comhem.se authored
-
- 08 Apr, 2005 1 commit
-
-
pem@mysql.comhem.se authored
and BUG#9074: STORED PROC: The scope of every handler declared is not properly applied
-
- 07 Apr, 2005 1 commit
-
-
dlenev@brandersnatch.localdomain authored
state" to sp-error.test. According to Per-Erik all SP related tests which should result in error should go into sp-error.test and not in sp.test, because we want to be able to run sp.test using normal client.
-
- 06 Apr, 2005 1 commit
-
-
dlenev@brandersnatch.localdomain authored
illegal state". We should not assume that mysql.proc table does not exist if we are unable to open it under LOCK TABLES or in prelocked mode (and remember this fact by setting mysql_proc_table_exists to zero).
-
- 30 Mar, 2005 1 commit
-
-
pem@mysql.comhem.se authored
Sedond attempt: Simply disallow CHECK in SPs, since it can't work.
-
- 22 Mar, 2005 1 commit
-
-
mysqldev@mysql.com authored
New privilege CREATE USER (CREATE_USER_ACL, Create_user_priv) added grant2.test: new tests (mostly backported from jani's patch) system_mysql_db.result, sp.result, grant2.result, grant.result: results updated
-
- 18 Mar, 2005 1 commit
-
-
pem@mysql.comhem.se authored
-
- 17 Mar, 2005 1 commit
-
-
mysqldev@mysql.com authored
transactional test removed sp_trans.test, sp_trans.result: new file
-
- 15 Mar, 2005 1 commit
-
-
sergefp@mysql.com authored
-
- 08 Mar, 2005 2 commits
-
-
Sinisa@sinisa.nasamreza.org authored
-
Sinisa@sinisa.nasamreza.org authored
-
- 07 Mar, 2005 2 commits
-
-
pem@mysql.comhem.se authored
-
pem@mysql.comhem.se authored
-
- 05 Mar, 2005 1 commit
-
-
Sinisa@sinisa.nasamreza.org authored
stored procedure, it is converted to DELETE.
-
- 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.
-
- 03 Mar, 2005 1 commit
-
-
konstantin@mysql.com authored
and bug#8849 "problem with insert statement with table alias's": make equality propagation work in stored procedures and prepared statements. Equality propagation can change AND/OR structure of ON expressions, so the fix is to provide each execution of PS/SP with it's own copy of AND/OR tree. We have been doing that already for WHERE clauses, now ON clauses are also copied.
-
- 02 Mar, 2005 1 commit
-
-
pem@mysql.comhem.se authored
of DROP PROCEDURE IF EXISTS statement.
-
- 25 Feb, 2005 2 commits
-
-
pem@mysql.comhem.se authored
-
pem@mysql.comhem.se authored
Have to thd->set_time() before each substatement execution, to make current_time() et al return different times within the same procedure.
-
- 24 Feb, 2005 2 commits
-
-
pem@mysql.comhem.se authored
The warning sent is by itself ok, the problem was rather why it wasn't sent on some other platforms... The real problem was that a total_warn_count which was inconsistent with warn_list was sent back with send_eof() during SP execution, which in turn cause a protocol error in mysqltest.
-
bell@51.0.168.192.in-addr.arpa authored
-
- 18 Feb, 2005 1 commit
-
-
pem@mysql.comhem.se authored
BUG#6642: Stored procedure crash if expression with set function BUG#7013: Stored procedure crash if group by ... with rollup BUG#7743: 'Lost connection to MySQL server during query' on Stored Procedure BUG#7992: SELECT .. INTO variable .. within Stored Procedure crashes the server BUG#8116: calling simple stored procedure twice in a row results in server crash Rolling back the item change list after each substatement in a procedure fixed the failing assert().
-
- 16 Feb, 2005 1 commit
-
-
pem@mysql.comhem.se authored
-
- 09 Feb, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
(used t3, moved after last bug, renamed)
-
- 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.
-