An error occurred fetching the project authors.
- 12 Jan, 2006 1 commit
-
-
anozdrin@mysql.com authored
-
- 08 Dec, 2005 1 commit
-
-
konstantin@mysql.com authored
to Crash": the bug was that due to non-standard name resolution precedence in stored procedures (See Bug#5967) a stored procedure variable took precedence over a table column when the arguments for VALUES() function were resolved. The implementation of VALUES() function was not designed to work with Item_splocal and crashed. VALUES() function is non-standard. It can refer to, and is meaningful for, table columns only. The patch disables SP variables as possible arguments of VALUES() function.
-
- 07 Dec, 2005 1 commit
-
-
anozdrin@mysql.com authored
according to the standard. The idea is to use Field-classes to implement stored routines variables. Also, we should provide facade to Item-hierarchy by Item_field class (it is necessary, since SRVs take part in expressions). The patch fixes the following bugs: - BUG#8702: Stored Procedures: No Error/Warning shown for inappropriate data type matching; - BUG#8768: Functions: For any unsigned data type, -ve values can be passed and returned; - BUG#8769: Functions: For Int datatypes, out of range values can be passed and returned; - BUG#9078: STORED PROCDURE: Decimal digits are not displayed when we use DECIMAL datatype; - BUG#9572: Stored procedures: variable type declarations ignored; - BUG#12903: upper function does not work inside a function; - BUG#13705: parameters to stored procedures are not verified; - BUG#13808: ENUM type stored procedure parameter accepts non-enumerated data; - BUG#13909: Varchar Stored Procedure Parameter always BINARY string (ignores CHARACTER SET); - BUG#14161: Stored procedure cannot retrieve bigint unsigned; - BUG#14188: BINARY variables have no 0x00 padding; - BUG#15148: Stored procedure variables accept non-scalar values;
-
- 03 Dec, 2005 1 commit
-
-
serg@serg.mylan authored
it's about mysql_admin_commands not being reexecution-safe (and CHECK still isn't)
-
- 02 Dec, 2005 2 commits
-
-
bell@sanja.is.com.ua authored
of SELECT from query begining, to be independet of query buffer allocation. Correct procedure used to find beginning of the current statement during parsing (BUG#14885).
-
pem@mysql.com authored
-
- 28 Nov, 2005 1 commit
-
-
timour@mysql.com authored
Post-review fixes according to Monty's review.
-
- 25 Nov, 2005 1 commit
-
-
pem@mysql.com authored
Post-review version. Some minor review fixes, but also changed the way some errors are handled: Don't return specific parse errors; instead always use the more general "table corrupt" error (amended accordingly).
-
- 23 Nov, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 22 Nov, 2005 2 commits
-
-
bell@sanja.is.com.ua authored
if inner routine has more local variables than outer one, and one of its last variables was used as argument to NOT operator". THD::spcont was non-0 when we were parsing stored routine/trigger definition during execution of another stored routine. This confused methods of Item_splocal and forced them use wrong runtime context. Fix ensures that we always have THD::spcont equal to zero during routine/trigger body parsing. This also allows to avoid problems with errors which occur during parsing and SQL exception handlers.
-
pem@mysql.com authored
-
- 18 Nov, 2005 1 commit
-
-
konstantin@mysql.com authored
password": additional fix, also make sure that a syntax error is returned for set names="foo" when there is no such variable or no stored procedure.
-
- 17 Nov, 2005 1 commit
-
-
pem@mysql.com authored
Since long, the compiled code of stored routines has been printed in the trace file when starting mysqld with the "--debug" flag. (At creation time only, and only in debug builds of course.) This has been helpful when debugging stored procedure execution, but it's a bit awkward to use. Also, the printing of some of the instructions is a bit terse, in particular for sp_instr_stmt where only the command code was printed. This improves the printout of several of the instructions, and adds the debugging- only commands "show procedure code <name>" and "show function code <name>". (In non-debug builds they are not available.)
-
- 16 Nov, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
Issuing error about presence of commit/rollback statements in stored functions and triggers added to SP parsing procedure (BUG#13627) The crash mentioned in original bug report is already prevented by one of previous patches (fix for bug #13343 "CREATE|etc TRIGGER|VIEW|USER don't commit the transaction (inconsistency)"), this patch only improve error returning.
-
- 10 Nov, 2005 1 commit
-
-
anozdrin@mysql.com authored
checks on trigger activation)
-
- 09 Nov, 2005 1 commit
-
-
pem@mysql.com authored
Corrected the syntax for the current_user() case. (It's "definer = current_user[()]", not just "current_user[()]".)
-
- 01 Nov, 2005 1 commit
-
-
pem@mysql.com authored
Added finer scope control for default clauses of local variable declarations.
-
- 28 Oct, 2005 1 commit
-
-
pem@mysql.com authored
Changed the parser test for wildcards in hostname to checking for empty strings instead (analogous with the test in default_view_definer()), since wildcards do appear in the definer's host-part sometimes.
-
- 25 Oct, 2005 2 commits
-
-
acurtis@zim.(none) authored
-
timour@mysql.com authored
The cause for the bug is that the priorities of all rules/terminals that process the FROM clause are not fully specified, and the parser generator produces a parser that doesn't always parse the FROM clause so that JOINs are left-associative. As a result the final join tree produced by the parser is incorrect, which is the cause for subsequent name resolution to fail.
-
- 24 Oct, 2005 1 commit
-
-
anozdrin@mysql.com authored
- allow CREATE VIEW as well as DROP VIEW to use in prepared statements; - fix CREATE VIEW implementation to make it work in prepared statements.
-
- 21 Oct, 2005 2 commits
-
-
bar@mysql.com authored
select distinct char(column) fails with utf8 ctype_utf8.result, ctype_utf8.test: Adding test case sql_yacc.yy: Adding new syntax. item_strfunc.h: Fixing wrong max_length calculation. Also, adding CHAR(x USING charset), for easier migrating from 4.1 to 5.0, according to Monty's suggestion.
-
andrey@lmy004. authored
ESCAPE has length of 1 if specified and sql_mode is NO_BACKSLASH_ESCAPES or has length of 0 or 1 in every other situation. (approved patch applied on a up-to-date tree re-commit)
-
- 15 Oct, 2005 2 commits
-
-
igor@rurik.mysql.com authored
allowed set functions aggregated in outer subqueries, allowed nested set functions.
-
hf@deer.(none) authored
-
- 13 Oct, 2005 1 commit
-
-
bar@mysql.com authored
New syntax: CHAR(x USING charset) Adding test case. sql_yacc.yy: New syntax: CHAR(x USING charset) Adding new parser rule. item_strfunc.h: New syntax: CHAR(x USING charset) Adding a new constructor.
-
- 12 Oct, 2005 1 commit
-
-
grog@mysql.com authored
Bug #10308: Parse 'purge master logs' with subselect correctly. subselect.test: Bug #10308: Test for 'purge master logs' with subselect. subselect.result: Bug #10308: Test result for 'purge master logs' with subselect.
-
- 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.
-
- 22 Sep, 2005 1 commit
-
-
ramil@mysql.com authored
-
- 20 Sep, 2005 2 commits
-
-
bell@sanja.is.com.ua authored
WL#2787 (Add view definer/owner to the view definition (.frm) to check privileges on used tables and stored routines when using a VIEW.) Part 2 postreview fixes.
-
ramil@mysql.com authored
-
- 19 Sep, 2005 1 commit
-
-
jonas@perch.ndb.mysql.com authored
that dump free list allocation per connection
-
- 15 Sep, 2005 1 commit
-
-
bell@sanja.is.com.ua authored
-
- 14 Sep, 2005 3 commits
-
-
sasha@asksasha.com authored
present): the problem originally was that the tables in auxilliary_tables did not have the correct real_name, which caused problems in the second call to tables_ok(). The fix corrects the real_name problem, and also sets the updating flag properly, which makes the second call to tables_ok() unnecessary.
-
pem@mysql.com authored
-
bell@sanja.is.com.ua authored
view definer information syntax/storage/replication fixed SOURCE field of .frm
-
- 13 Sep, 2005 3 commits
-
-
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).
-
pem@mysql.com authored
Have to init. all local variables in their frames, not just once at the beginning of invocation.
-
eric@mysql.com authored
(per Monty's patch). Remove references to the "COMMENT" field. WL#2414
-
- 10 Sep, 2005 1 commit
-
-
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.
-