Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
/* Copyright (C) 2002 MySQL AB
|
|
|
|
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
|
|
it under the terms of the GNU General Public License as published by
|
2006-12-23 20:17:15 +01:00
|
|
|
the Free Software Foundation; version 2 of the License.
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
|
|
|
|
This program is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
along with this program; if not, write to the Free Software
|
|
|
|
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA */
|
|
|
|
|
2005-06-05 16:20:22 +02:00
|
|
|
#include "mysql_priv.h"
|
2005-05-27 12:03:37 +02:00
|
|
|
#ifdef USE_PRAGMA_IMPLEMENTATION
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
#pragma implementation
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#if defined(WIN32) || defined(__WIN__)
|
|
|
|
#undef SAFEMALLOC /* Problems with threads */
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#include "sp_pcontext.h"
|
2002-12-11 14:24:29 +01:00
|
|
|
#include "sp_head.h"
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
|
Bug#26503 (Illegal SQL exception handler code causes the server to crash)
Before this fix, the parser would accept illegal code in SQL exceptions
handlers, that later causes the runtime to crash when executing the code,
due to memory violations in the exception handler stack.
The root cause of the problem is instructions within an exception handler
that jumps to code located outside of the handler. This is illegal according
to the SQL 2003 standard, since labels located outside the handler are not
supposed to be visible (they are "out of scope"), so any instruction that
jumps to these labels, like ITERATE or LEAVE, should not parse.
The section of the standard that is relevant for this is :
SQL:2003 SQL/PSM (ISO/IEC 9075-4:2003)
section 13.1 <compound statement>,
syntax rule 4
<quote>
The scope of the <beginning label> is CS excluding every <SQL schema
statement> contained in CS and excluding every
<local handler declaration list> contained in CS. <beginning label> shall
not be equivalent to any other <beginning label>s within that scope.
</quote>
With this fix, the C++ class sp_pcontext, which represent the "parsing
context" tree (a.k.a symbol table) of a stored procedure, has been changed
as follows:
- constructors have been cleaned up, so that only building a root node for
the tree is public; building nodes inside a tree is not public.
- a new member, m_label_scope, indicates if a given syntactic context
belongs to a DECLARE HANDLER block,
- label resolution, in the method find_label(), has been changed to
implement the restriction of scope regarding labels used in a compound
statement.
The actions in the parser, when parsing the body of a SQL exception handler,
have been changed as follows:
- the implementation of an exception handler (DECLARE HANDLER) now creates
explicitly a new sp_pcontext, to isolate the code inside the handler from
the containing compound statement context.
- registering exception handlers as a result occurs in the parent context,
see the rule sp_hcond_element
- the code in sp_hcond_list has been cleaned up, to avoid code duplication
In addition, the flags IN_SIMPLE_CASE and IN_HANDLER, declared in sp_head.h
have been removed, since they are unused and broken by design (as seen with
Bug 19194 (Right recursion in parser for CASE causes excessive stack usage,
limitation), representing a stack in a single flag is not possible.
Tests in sp-error have been added to show that illegal constructs are now
rejected.
Tests in sp have been added for code coverage, to show that ITERATE or LEAVE
statements are legal when jumping to a label in scope, inside the body of
an exception handler.
2007-03-14 19:02:32 +01:00
|
|
|
/* Initial size for the dynamic arrays in sp_pcontext */
|
|
|
|
#define PCONTEXT_ARRAY_INIT_ALLOC 16
|
|
|
|
/* Increment size for the dynamic arrays in sp_pcontext */
|
|
|
|
#define PCONTEXT_ARRAY_INCREMENT_ALLOC 8
|
|
|
|
|
2005-02-28 18:07:06 +01:00
|
|
|
/*
|
2006-04-07 16:53:15 +02:00
|
|
|
Sanity check for SQLSTATEs. Will not check if it's really an existing
|
|
|
|
state (there are just too many), but will check length and bad characters.
|
|
|
|
Returns TRUE if it's ok, FALSE if it's bad.
|
|
|
|
*/
|
2005-02-28 18:07:06 +01:00
|
|
|
bool
|
|
|
|
sp_cond_check(LEX_STRING *sqlstate)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
const char *p;
|
|
|
|
|
|
|
|
if (sqlstate->length != 5)
|
|
|
|
return FALSE;
|
|
|
|
for (p= sqlstate->str, i= 0 ; i < 5 ; i++)
|
|
|
|
{
|
|
|
|
char c = p[i];
|
|
|
|
|
|
|
|
if ((c < '0' || '9' < c) &&
|
|
|
|
(c < 'A' || 'Z' < c))
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
Bug#26503 (Illegal SQL exception handler code causes the server to crash)
Before this fix, the parser would accept illegal code in SQL exceptions
handlers, that later causes the runtime to crash when executing the code,
due to memory violations in the exception handler stack.
The root cause of the problem is instructions within an exception handler
that jumps to code located outside of the handler. This is illegal according
to the SQL 2003 standard, since labels located outside the handler are not
supposed to be visible (they are "out of scope"), so any instruction that
jumps to these labels, like ITERATE or LEAVE, should not parse.
The section of the standard that is relevant for this is :
SQL:2003 SQL/PSM (ISO/IEC 9075-4:2003)
section 13.1 <compound statement>,
syntax rule 4
<quote>
The scope of the <beginning label> is CS excluding every <SQL schema
statement> contained in CS and excluding every
<local handler declaration list> contained in CS. <beginning label> shall
not be equivalent to any other <beginning label>s within that scope.
</quote>
With this fix, the C++ class sp_pcontext, which represent the "parsing
context" tree (a.k.a symbol table) of a stored procedure, has been changed
as follows:
- constructors have been cleaned up, so that only building a root node for
the tree is public; building nodes inside a tree is not public.
- a new member, m_label_scope, indicates if a given syntactic context
belongs to a DECLARE HANDLER block,
- label resolution, in the method find_label(), has been changed to
implement the restriction of scope regarding labels used in a compound
statement.
The actions in the parser, when parsing the body of a SQL exception handler,
have been changed as follows:
- the implementation of an exception handler (DECLARE HANDLER) now creates
explicitly a new sp_pcontext, to isolate the code inside the handler from
the containing compound statement context.
- registering exception handlers as a result occurs in the parent context,
see the rule sp_hcond_element
- the code in sp_hcond_list has been cleaned up, to avoid code duplication
In addition, the flags IN_SIMPLE_CASE and IN_HANDLER, declared in sp_head.h
have been removed, since they are unused and broken by design (as seen with
Bug 19194 (Right recursion in parser for CASE causes excessive stack usage,
limitation), representing a stack in a single flag is not possible.
Tests in sp-error have been added to show that illegal constructs are now
rejected.
Tests in sp have been added for code coverage, to show that ITERATE or LEAVE
statements are legal when jumping to a label in scope, inside the body of
an exception handler.
2007-03-14 19:02:32 +01:00
|
|
|
sp_pcontext::sp_pcontext()
|
|
|
|
: Sql_alloc(),
|
|
|
|
m_max_var_index(0), m_max_cursor_index(0), m_max_handler_index(0),
|
|
|
|
m_context_handlers(0), m_parent(NULL), m_pboundary(0),
|
|
|
|
m_label_scope(LABEL_DEFAULT_SCOPE)
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
{
|
Bug#26503 (Illegal SQL exception handler code causes the server to crash)
Before this fix, the parser would accept illegal code in SQL exceptions
handlers, that later causes the runtime to crash when executing the code,
due to memory violations in the exception handler stack.
The root cause of the problem is instructions within an exception handler
that jumps to code located outside of the handler. This is illegal according
to the SQL 2003 standard, since labels located outside the handler are not
supposed to be visible (they are "out of scope"), so any instruction that
jumps to these labels, like ITERATE or LEAVE, should not parse.
The section of the standard that is relevant for this is :
SQL:2003 SQL/PSM (ISO/IEC 9075-4:2003)
section 13.1 <compound statement>,
syntax rule 4
<quote>
The scope of the <beginning label> is CS excluding every <SQL schema
statement> contained in CS and excluding every
<local handler declaration list> contained in CS. <beginning label> shall
not be equivalent to any other <beginning label>s within that scope.
</quote>
With this fix, the C++ class sp_pcontext, which represent the "parsing
context" tree (a.k.a symbol table) of a stored procedure, has been changed
as follows:
- constructors have been cleaned up, so that only building a root node for
the tree is public; building nodes inside a tree is not public.
- a new member, m_label_scope, indicates if a given syntactic context
belongs to a DECLARE HANDLER block,
- label resolution, in the method find_label(), has been changed to
implement the restriction of scope regarding labels used in a compound
statement.
The actions in the parser, when parsing the body of a SQL exception handler,
have been changed as follows:
- the implementation of an exception handler (DECLARE HANDLER) now creates
explicitly a new sp_pcontext, to isolate the code inside the handler from
the containing compound statement context.
- registering exception handlers as a result occurs in the parent context,
see the rule sp_hcond_element
- the code in sp_hcond_list has been cleaned up, to avoid code duplication
In addition, the flags IN_SIMPLE_CASE and IN_HANDLER, declared in sp_head.h
have been removed, since they are unused and broken by design (as seen with
Bug 19194 (Right recursion in parser for CASE causes excessive stack usage,
limitation), representing a stack in a single flag is not possible.
Tests in sp-error have been added to show that illegal constructs are now
rejected.
Tests in sp have been added for code coverage, to show that ITERATE or LEAVE
statements are legal when jumping to a label in scope, inside the body of
an exception handler.
2007-03-14 19:02:32 +01:00
|
|
|
VOID(my_init_dynamic_array(&m_vars, sizeof(sp_variable_t *),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
|
|
|
VOID(my_init_dynamic_array(&m_case_expr_id_lst, sizeof(int),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
|
|
|
VOID(my_init_dynamic_array(&m_conds, sizeof(sp_cond_type_t *),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
|
|
|
VOID(my_init_dynamic_array(&m_cursors, sizeof(LEX_STRING),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
|
|
|
VOID(my_init_dynamic_array(&m_handlers, sizeof(sp_cond_type_t *),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
2002-12-11 14:24:29 +01:00
|
|
|
m_label.empty();
|
2004-08-26 12:54:30 +02:00
|
|
|
m_children.empty();
|
Bug#26503 (Illegal SQL exception handler code causes the server to crash)
Before this fix, the parser would accept illegal code in SQL exceptions
handlers, that later causes the runtime to crash when executing the code,
due to memory violations in the exception handler stack.
The root cause of the problem is instructions within an exception handler
that jumps to code located outside of the handler. This is illegal according
to the SQL 2003 standard, since labels located outside the handler are not
supposed to be visible (they are "out of scope"), so any instruction that
jumps to these labels, like ITERATE or LEAVE, should not parse.
The section of the standard that is relevant for this is :
SQL:2003 SQL/PSM (ISO/IEC 9075-4:2003)
section 13.1 <compound statement>,
syntax rule 4
<quote>
The scope of the <beginning label> is CS excluding every <SQL schema
statement> contained in CS and excluding every
<local handler declaration list> contained in CS. <beginning label> shall
not be equivalent to any other <beginning label>s within that scope.
</quote>
With this fix, the C++ class sp_pcontext, which represent the "parsing
context" tree (a.k.a symbol table) of a stored procedure, has been changed
as follows:
- constructors have been cleaned up, so that only building a root node for
the tree is public; building nodes inside a tree is not public.
- a new member, m_label_scope, indicates if a given syntactic context
belongs to a DECLARE HANDLER block,
- label resolution, in the method find_label(), has been changed to
implement the restriction of scope regarding labels used in a compound
statement.
The actions in the parser, when parsing the body of a SQL exception handler,
have been changed as follows:
- the implementation of an exception handler (DECLARE HANDLER) now creates
explicitly a new sp_pcontext, to isolate the code inside the handler from
the containing compound statement context.
- registering exception handlers as a result occurs in the parent context,
see the rule sp_hcond_element
- the code in sp_hcond_list has been cleaned up, to avoid code duplication
In addition, the flags IN_SIMPLE_CASE and IN_HANDLER, declared in sp_head.h
have been removed, since they are unused and broken by design (as seen with
Bug 19194 (Right recursion in parser for CASE causes excessive stack usage,
limitation), representing a stack in a single flag is not possible.
Tests in sp-error have been added to show that illegal constructs are now
rejected.
Tests in sp have been added for code coverage, to show that ITERATE or LEAVE
statements are legal when jumping to a label in scope, inside the body of
an exception handler.
2007-03-14 19:02:32 +01:00
|
|
|
|
|
|
|
m_var_offset= m_cursor_offset= 0;
|
|
|
|
m_num_case_exprs= 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
sp_pcontext::sp_pcontext(sp_pcontext *prev, label_scope_type label_scope)
|
|
|
|
: Sql_alloc(),
|
|
|
|
m_max_var_index(0), m_max_cursor_index(0), m_max_handler_index(0),
|
|
|
|
m_context_handlers(0), m_parent(prev), m_pboundary(0),
|
|
|
|
m_label_scope(label_scope)
|
|
|
|
{
|
|
|
|
VOID(my_init_dynamic_array(&m_vars, sizeof(sp_variable_t *),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
|
|
|
VOID(my_init_dynamic_array(&m_case_expr_id_lst, sizeof(int),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
|
|
|
VOID(my_init_dynamic_array(&m_conds, sizeof(sp_cond_type_t *),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
|
|
|
VOID(my_init_dynamic_array(&m_cursors, sizeof(LEX_STRING),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
|
|
|
VOID(my_init_dynamic_array(&m_handlers, sizeof(sp_cond_type_t *),
|
|
|
|
PCONTEXT_ARRAY_INIT_ALLOC,
|
|
|
|
PCONTEXT_ARRAY_INCREMENT_ALLOC));
|
|
|
|
m_label.empty();
|
|
|
|
m_children.empty();
|
|
|
|
|
|
|
|
m_var_offset= prev->m_var_offset + prev->m_max_var_index;
|
|
|
|
m_cursor_offset= prev->current_cursor_count();
|
|
|
|
m_num_case_exprs= prev->get_num_case_exprs();
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
void
|
2003-04-02 20:42:28 +02:00
|
|
|
sp_pcontext::destroy()
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
{
|
2004-08-26 12:54:30 +02:00
|
|
|
List_iterator_fast<sp_pcontext> li(m_children);
|
|
|
|
sp_pcontext *child;
|
|
|
|
|
|
|
|
while ((child= li++))
|
|
|
|
child->destroy();
|
|
|
|
|
|
|
|
m_children.empty();
|
|
|
|
m_label.empty();
|
2006-04-07 16:53:15 +02:00
|
|
|
delete_dynamic(&m_vars);
|
2005-12-07 15:01:17 +01:00
|
|
|
delete_dynamic(&m_case_expr_id_lst);
|
2006-04-07 16:53:15 +02:00
|
|
|
delete_dynamic(&m_conds);
|
|
|
|
delete_dynamic(&m_cursors);
|
|
|
|
delete_dynamic(&m_handlers);
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
}
|
|
|
|
|
2004-08-26 12:54:30 +02:00
|
|
|
sp_pcontext *
|
Bug#26503 (Illegal SQL exception handler code causes the server to crash)
Before this fix, the parser would accept illegal code in SQL exceptions
handlers, that later causes the runtime to crash when executing the code,
due to memory violations in the exception handler stack.
The root cause of the problem is instructions within an exception handler
that jumps to code located outside of the handler. This is illegal according
to the SQL 2003 standard, since labels located outside the handler are not
supposed to be visible (they are "out of scope"), so any instruction that
jumps to these labels, like ITERATE or LEAVE, should not parse.
The section of the standard that is relevant for this is :
SQL:2003 SQL/PSM (ISO/IEC 9075-4:2003)
section 13.1 <compound statement>,
syntax rule 4
<quote>
The scope of the <beginning label> is CS excluding every <SQL schema
statement> contained in CS and excluding every
<local handler declaration list> contained in CS. <beginning label> shall
not be equivalent to any other <beginning label>s within that scope.
</quote>
With this fix, the C++ class sp_pcontext, which represent the "parsing
context" tree (a.k.a symbol table) of a stored procedure, has been changed
as follows:
- constructors have been cleaned up, so that only building a root node for
the tree is public; building nodes inside a tree is not public.
- a new member, m_label_scope, indicates if a given syntactic context
belongs to a DECLARE HANDLER block,
- label resolution, in the method find_label(), has been changed to
implement the restriction of scope regarding labels used in a compound
statement.
The actions in the parser, when parsing the body of a SQL exception handler,
have been changed as follows:
- the implementation of an exception handler (DECLARE HANDLER) now creates
explicitly a new sp_pcontext, to isolate the code inside the handler from
the containing compound statement context.
- registering exception handlers as a result occurs in the parent context,
see the rule sp_hcond_element
- the code in sp_hcond_list has been cleaned up, to avoid code duplication
In addition, the flags IN_SIMPLE_CASE and IN_HANDLER, declared in sp_head.h
have been removed, since they are unused and broken by design (as seen with
Bug 19194 (Right recursion in parser for CASE causes excessive stack usage,
limitation), representing a stack in a single flag is not possible.
Tests in sp-error have been added to show that illegal constructs are now
rejected.
Tests in sp have been added for code coverage, to show that ITERATE or LEAVE
statements are legal when jumping to a label in scope, inside the body of
an exception handler.
2007-03-14 19:02:32 +01:00
|
|
|
sp_pcontext::push_context(label_scope_type label_scope)
|
2003-11-13 19:34:56 +01:00
|
|
|
{
|
Bug#26503 (Illegal SQL exception handler code causes the server to crash)
Before this fix, the parser would accept illegal code in SQL exceptions
handlers, that later causes the runtime to crash when executing the code,
due to memory violations in the exception handler stack.
The root cause of the problem is instructions within an exception handler
that jumps to code located outside of the handler. This is illegal according
to the SQL 2003 standard, since labels located outside the handler are not
supposed to be visible (they are "out of scope"), so any instruction that
jumps to these labels, like ITERATE or LEAVE, should not parse.
The section of the standard that is relevant for this is :
SQL:2003 SQL/PSM (ISO/IEC 9075-4:2003)
section 13.1 <compound statement>,
syntax rule 4
<quote>
The scope of the <beginning label> is CS excluding every <SQL schema
statement> contained in CS and excluding every
<local handler declaration list> contained in CS. <beginning label> shall
not be equivalent to any other <beginning label>s within that scope.
</quote>
With this fix, the C++ class sp_pcontext, which represent the "parsing
context" tree (a.k.a symbol table) of a stored procedure, has been changed
as follows:
- constructors have been cleaned up, so that only building a root node for
the tree is public; building nodes inside a tree is not public.
- a new member, m_label_scope, indicates if a given syntactic context
belongs to a DECLARE HANDLER block,
- label resolution, in the method find_label(), has been changed to
implement the restriction of scope regarding labels used in a compound
statement.
The actions in the parser, when parsing the body of a SQL exception handler,
have been changed as follows:
- the implementation of an exception handler (DECLARE HANDLER) now creates
explicitly a new sp_pcontext, to isolate the code inside the handler from
the containing compound statement context.
- registering exception handlers as a result occurs in the parent context,
see the rule sp_hcond_element
- the code in sp_hcond_list has been cleaned up, to avoid code duplication
In addition, the flags IN_SIMPLE_CASE and IN_HANDLER, declared in sp_head.h
have been removed, since they are unused and broken by design (as seen with
Bug 19194 (Right recursion in parser for CASE causes excessive stack usage,
limitation), representing a stack in a single flag is not possible.
Tests in sp-error have been added to show that illegal constructs are now
rejected.
Tests in sp have been added for code coverage, to show that ITERATE or LEAVE
statements are legal when jumping to a label in scope, inside the body of
an exception handler.
2007-03-14 19:02:32 +01:00
|
|
|
sp_pcontext *child= new sp_pcontext(this, label_scope);
|
2004-08-26 12:54:30 +02:00
|
|
|
|
|
|
|
if (child)
|
|
|
|
m_children.push_back(child);
|
|
|
|
return child;
|
2003-11-13 19:34:56 +01:00
|
|
|
}
|
|
|
|
|
2004-08-26 12:54:30 +02:00
|
|
|
sp_pcontext *
|
|
|
|
sp_pcontext::pop_context()
|
2003-11-13 19:34:56 +01:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
m_parent->m_max_var_index+= m_max_var_index;
|
2004-08-26 12:54:30 +02:00
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
uint submax= max_handler_index();
|
|
|
|
if (submax > m_parent->m_max_handler_index)
|
|
|
|
m_parent->m_max_handler_index= submax;
|
2005-12-07 15:01:17 +01:00
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
submax= max_cursor_index();
|
|
|
|
if (submax > m_parent->m_max_cursor_index)
|
|
|
|
m_parent->m_max_cursor_index= submax;
|
2005-12-07 15:01:17 +01:00
|
|
|
|
|
|
|
if (m_num_case_exprs > m_parent->m_num_case_exprs)
|
|
|
|
m_parent->m_num_case_exprs= m_num_case_exprs;
|
|
|
|
|
2004-08-26 12:54:30 +02:00
|
|
|
return m_parent;
|
2004-08-17 20:20:58 +02:00
|
|
|
}
|
|
|
|
|
2004-08-26 12:54:30 +02:00
|
|
|
uint
|
2006-02-15 12:11:29 +01:00
|
|
|
sp_pcontext::diff_handlers(sp_pcontext *ctx, bool exclusive)
|
2004-08-17 20:20:58 +02:00
|
|
|
{
|
2004-08-26 12:54:30 +02:00
|
|
|
uint n= 0;
|
|
|
|
sp_pcontext *pctx= this;
|
2006-02-15 12:11:29 +01:00
|
|
|
sp_pcontext *last_ctx= NULL;
|
2004-08-17 20:20:58 +02:00
|
|
|
|
2004-08-26 12:54:30 +02:00
|
|
|
while (pctx && pctx != ctx)
|
2004-08-17 20:20:58 +02:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
n+= pctx->m_context_handlers;
|
2006-02-15 12:11:29 +01:00
|
|
|
last_ctx= pctx;
|
2004-08-26 12:54:30 +02:00
|
|
|
pctx= pctx->parent_context();
|
2004-08-17 20:20:58 +02:00
|
|
|
}
|
2004-08-26 12:54:30 +02:00
|
|
|
if (pctx)
|
2006-04-07 16:53:15 +02:00
|
|
|
return (exclusive && last_ctx ? n - last_ctx->m_context_handlers : n);
|
2004-08-26 12:54:30 +02:00
|
|
|
return 0; // Didn't find ctx
|
|
|
|
}
|
|
|
|
|
|
|
|
uint
|
2006-02-15 12:11:29 +01:00
|
|
|
sp_pcontext::diff_cursors(sp_pcontext *ctx, bool exclusive)
|
2004-08-26 12:54:30 +02:00
|
|
|
{
|
2006-02-15 12:11:29 +01:00
|
|
|
uint n= 0;
|
2004-08-26 12:54:30 +02:00
|
|
|
sp_pcontext *pctx= this;
|
2006-02-15 12:11:29 +01:00
|
|
|
sp_pcontext *last_ctx= NULL;
|
2004-08-26 12:54:30 +02:00
|
|
|
|
|
|
|
while (pctx && pctx != ctx)
|
2006-02-15 12:11:29 +01:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
n+= pctx->m_cursors.elements;
|
2006-02-15 12:11:29 +01:00
|
|
|
last_ctx= pctx;
|
2004-08-26 12:54:30 +02:00
|
|
|
pctx= pctx->parent_context();
|
2006-02-15 12:11:29 +01:00
|
|
|
}
|
2004-08-26 12:54:30 +02:00
|
|
|
if (pctx)
|
2006-04-07 16:53:15 +02:00
|
|
|
return (exclusive && last_ctx ? n - last_ctx->m_cursors.elements : n);
|
2004-08-26 12:54:30 +02:00
|
|
|
return 0; // Didn't find ctx
|
2003-11-13 19:34:56 +01:00
|
|
|
}
|
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
/*
|
|
|
|
This does a linear search (from newer to older variables, in case
|
|
|
|
we have shadowed names).
|
|
|
|
It's possible to have a more efficient allocation and search method,
|
|
|
|
but it might not be worth it. The typical number of parameters and
|
|
|
|
variables will in most cases be low (a handfull).
|
|
|
|
...and, this is only called during parsing.
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
*/
|
2006-04-07 16:53:15 +02:00
|
|
|
sp_variable_t *
|
|
|
|
sp_pcontext::find_variable(LEX_STRING *name, my_bool scoped)
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
uint i= m_vars.elements - m_pboundary;
|
2003-11-13 19:34:56 +01:00
|
|
|
|
2004-08-26 12:54:30 +02:00
|
|
|
while (i--)
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
sp_variable_t *p;
|
2003-03-20 11:57:05 +01:00
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
get_dynamic(&m_vars, (gptr)&p, i);
|
2003-04-04 15:47:43 +02:00
|
|
|
if (my_strnncoll(system_charset_info,
|
|
|
|
(const uchar *)name->str, name->length,
|
|
|
|
(const uchar *)p->name.str, p->name.length) == 0)
|
2003-03-19 11:36:32 +01:00
|
|
|
{
|
2003-04-02 20:42:28 +02:00
|
|
|
return p;
|
2003-03-19 11:36:32 +01:00
|
|
|
}
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
}
|
2004-08-26 12:54:30 +02:00
|
|
|
if (!scoped && m_parent)
|
2006-04-07 16:53:15 +02:00
|
|
|
return m_parent->find_variable(name, scoped);
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
2005-11-17 11:11:48 +01:00
|
|
|
/*
|
|
|
|
Find a variable by offset from the top.
|
|
|
|
This used for two things:
|
|
|
|
- When evaluating parameters at the beginning, and setting out parameters
|
|
|
|
at the end, of invokation. (Top frame only, so no recursion then.)
|
|
|
|
- For printing of sp_instr_set. (Debug mode only.)
|
2006-04-07 16:53:15 +02:00
|
|
|
*/
|
|
|
|
sp_variable_t *
|
|
|
|
sp_pcontext::find_variable(uint offset)
|
2005-11-17 11:11:48 +01:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
if (m_var_offset <= offset && offset < m_var_offset + m_vars.elements)
|
2005-11-17 11:11:48 +01:00
|
|
|
{ // This frame
|
2006-04-07 16:53:15 +02:00
|
|
|
sp_variable_t *p;
|
2005-11-17 11:11:48 +01:00
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
get_dynamic(&m_vars, (gptr)&p, offset - m_var_offset);
|
2005-11-17 11:11:48 +01:00
|
|
|
return p;
|
|
|
|
}
|
2005-11-18 16:30:27 +01:00
|
|
|
if (m_parent)
|
2006-04-07 16:53:15 +02:00
|
|
|
return m_parent->find_variable(offset); // Some previous frame
|
2005-11-18 16:30:27 +01:00
|
|
|
return NULL; // index out of bounds
|
2005-11-17 11:11:48 +01:00
|
|
|
}
|
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
sp_variable_t *
|
|
|
|
sp_pcontext::push_variable(LEX_STRING *name, enum enum_field_types type,
|
|
|
|
sp_param_mode_t mode)
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
sp_variable_t *p= (sp_variable_t *)sql_alloc(sizeof(sp_variable_t));
|
2003-04-02 20:42:28 +02:00
|
|
|
|
2005-12-07 15:01:17 +01:00
|
|
|
if (!p)
|
|
|
|
return NULL;
|
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
++m_max_var_index;
|
2005-12-07 15:01:17 +01:00
|
|
|
|
|
|
|
p->name.str= name->str;
|
|
|
|
p->name.length= name->length;
|
|
|
|
p->type= type;
|
|
|
|
p->mode= mode;
|
2006-04-07 16:53:15 +02:00
|
|
|
p->offset= current_var_count();
|
2005-12-07 15:01:17 +01:00
|
|
|
p->dflt= NULL;
|
2006-04-07 16:53:15 +02:00
|
|
|
insert_dynamic(&m_vars, (gptr)&p);
|
2005-12-07 15:01:17 +01:00
|
|
|
|
|
|
|
return p;
|
Simplistic, experimental framework for Stored Procedures (SPs).
Implements creation and dropping of PROCEDUREs, IN, OUT, and INOUT parameters,
single-statement procedures, rudimentary multi-statement (begin-end) prodedures
(when the client can handle it), and local variables.
Missing most of the embedded SQL language, all attributes, FUNCTIONs, error handling,
reparses procedures at each call (no caching), etc, etc.
Certainly buggy too, but procedures can actually be created and called....
2002-12-08 19:59:22 +01:00
|
|
|
}
|
2002-12-11 14:24:29 +01:00
|
|
|
|
2005-12-07 15:01:17 +01:00
|
|
|
|
2002-12-16 15:40:44 +01:00
|
|
|
sp_label_t *
|
2002-12-11 14:24:29 +01:00
|
|
|
sp_pcontext::push_label(char *name, uint ip)
|
|
|
|
{
|
2003-04-02 20:42:28 +02:00
|
|
|
sp_label_t *lab = (sp_label_t *)sql_alloc(sizeof(sp_label_t));
|
2002-12-11 14:24:29 +01:00
|
|
|
|
|
|
|
if (lab)
|
|
|
|
{
|
|
|
|
lab->name= name;
|
|
|
|
lab->ip= ip;
|
2006-04-18 11:07:34 +02:00
|
|
|
lab->type= SP_LAB_IMPL;
|
2004-08-26 12:54:30 +02:00
|
|
|
lab->ctx= this;
|
2002-12-11 14:24:29 +01:00
|
|
|
m_label.push_front(lab);
|
|
|
|
}
|
2002-12-16 15:40:44 +01:00
|
|
|
return lab;
|
2002-12-11 14:24:29 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
sp_label_t *
|
|
|
|
sp_pcontext::find_label(char *name)
|
|
|
|
{
|
|
|
|
List_iterator_fast<sp_label_t> li(m_label);
|
|
|
|
sp_label_t *lab;
|
|
|
|
|
|
|
|
while ((lab= li++))
|
2003-03-27 17:35:27 +01:00
|
|
|
if (my_strcasecmp(system_charset_info, name, lab->name) == 0)
|
2002-12-11 14:24:29 +01:00
|
|
|
return lab;
|
|
|
|
|
Bug#26503 (Illegal SQL exception handler code causes the server to crash)
Before this fix, the parser would accept illegal code in SQL exceptions
handlers, that later causes the runtime to crash when executing the code,
due to memory violations in the exception handler stack.
The root cause of the problem is instructions within an exception handler
that jumps to code located outside of the handler. This is illegal according
to the SQL 2003 standard, since labels located outside the handler are not
supposed to be visible (they are "out of scope"), so any instruction that
jumps to these labels, like ITERATE or LEAVE, should not parse.
The section of the standard that is relevant for this is :
SQL:2003 SQL/PSM (ISO/IEC 9075-4:2003)
section 13.1 <compound statement>,
syntax rule 4
<quote>
The scope of the <beginning label> is CS excluding every <SQL schema
statement> contained in CS and excluding every
<local handler declaration list> contained in CS. <beginning label> shall
not be equivalent to any other <beginning label>s within that scope.
</quote>
With this fix, the C++ class sp_pcontext, which represent the "parsing
context" tree (a.k.a symbol table) of a stored procedure, has been changed
as follows:
- constructors have been cleaned up, so that only building a root node for
the tree is public; building nodes inside a tree is not public.
- a new member, m_label_scope, indicates if a given syntactic context
belongs to a DECLARE HANDLER block,
- label resolution, in the method find_label(), has been changed to
implement the restriction of scope regarding labels used in a compound
statement.
The actions in the parser, when parsing the body of a SQL exception handler,
have been changed as follows:
- the implementation of an exception handler (DECLARE HANDLER) now creates
explicitly a new sp_pcontext, to isolate the code inside the handler from
the containing compound statement context.
- registering exception handlers as a result occurs in the parent context,
see the rule sp_hcond_element
- the code in sp_hcond_list has been cleaned up, to avoid code duplication
In addition, the flags IN_SIMPLE_CASE and IN_HANDLER, declared in sp_head.h
have been removed, since they are unused and broken by design (as seen with
Bug 19194 (Right recursion in parser for CASE causes excessive stack usage,
limitation), representing a stack in a single flag is not possible.
Tests in sp-error have been added to show that illegal constructs are now
rejected.
Tests in sp have been added for code coverage, to show that ITERATE or LEAVE
statements are legal when jumping to a label in scope, inside the body of
an exception handler.
2007-03-14 19:02:32 +01:00
|
|
|
/*
|
|
|
|
Note about exception handlers.
|
|
|
|
See SQL:2003 SQL/PSM (ISO/IEC 9075-4:2003),
|
|
|
|
section 13.1 <compound statement>,
|
|
|
|
syntax rule 4.
|
|
|
|
In short, a DECLARE HANDLER block can not refer
|
|
|
|
to labels from the parent context, as they are out of scope.
|
|
|
|
*/
|
|
|
|
if (m_parent && (m_label_scope == LABEL_DEFAULT_SCOPE))
|
2004-08-26 12:54:30 +02:00
|
|
|
return m_parent->find_label(name);
|
2002-12-11 14:24:29 +01:00
|
|
|
return NULL;
|
|
|
|
}
|
2003-09-16 14:26:08 +02:00
|
|
|
|
|
|
|
void
|
|
|
|
sp_pcontext::push_cond(LEX_STRING *name, sp_cond_type_t *val)
|
|
|
|
{
|
|
|
|
sp_cond_t *p= (sp_cond_t *)sql_alloc(sizeof(sp_cond_t));
|
|
|
|
|
|
|
|
if (p)
|
|
|
|
{
|
|
|
|
p->name.str= name->str;
|
|
|
|
p->name.length= name->length;
|
|
|
|
p->val= val;
|
2006-04-07 16:53:15 +02:00
|
|
|
insert_dynamic(&m_conds, (gptr)&p);
|
2003-09-16 14:26:08 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2006-04-07 16:53:15 +02:00
|
|
|
See comment for find_variable() above
|
|
|
|
*/
|
2003-09-16 14:26:08 +02:00
|
|
|
sp_cond_type_t *
|
2003-11-13 19:34:56 +01:00
|
|
|
sp_pcontext::find_cond(LEX_STRING *name, my_bool scoped)
|
2003-09-16 14:26:08 +02:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
uint i= m_conds.elements;
|
2003-09-16 14:26:08 +02:00
|
|
|
|
2004-08-26 12:54:30 +02:00
|
|
|
while (i--)
|
2003-09-16 14:26:08 +02:00
|
|
|
{
|
|
|
|
sp_cond_t *p;
|
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
get_dynamic(&m_conds, (gptr)&p, i);
|
2003-09-16 14:26:08 +02:00
|
|
|
if (my_strnncoll(system_charset_info,
|
|
|
|
(const uchar *)name->str, name->length,
|
|
|
|
(const uchar *)p->name.str, p->name.length) == 0)
|
|
|
|
{
|
|
|
|
return p->val;
|
|
|
|
}
|
|
|
|
}
|
2004-08-26 12:54:30 +02:00
|
|
|
if (!scoped && m_parent)
|
|
|
|
return m_parent->find_cond(name, scoped);
|
2003-09-16 14:26:08 +02:00
|
|
|
return NULL;
|
|
|
|
}
|
2003-10-10 16:57:21 +02:00
|
|
|
|
2005-04-08 19:58:04 +02:00
|
|
|
/*
|
2006-04-07 16:53:15 +02:00
|
|
|
This only searches the current context, for error checking of
|
|
|
|
duplicates.
|
|
|
|
Returns TRUE if found.
|
|
|
|
*/
|
2005-04-08 19:58:04 +02:00
|
|
|
bool
|
|
|
|
sp_pcontext::find_handler(sp_cond_type_t *cond)
|
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
uint i= m_handlers.elements;
|
2005-04-08 19:58:04 +02:00
|
|
|
|
|
|
|
while (i--)
|
|
|
|
{
|
|
|
|
sp_cond_type_t *p;
|
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
get_dynamic(&m_handlers, (gptr)&p, i);
|
2005-04-08 19:58:04 +02:00
|
|
|
if (cond->type == p->type)
|
|
|
|
{
|
|
|
|
switch (p->type)
|
|
|
|
{
|
|
|
|
case sp_cond_type_t::number:
|
|
|
|
if (cond->mysqlerr == p->mysqlerr)
|
|
|
|
return TRUE;
|
|
|
|
break;
|
|
|
|
case sp_cond_type_t::state:
|
|
|
|
if (strcmp(cond->sqlstate, p->sqlstate) == 0)
|
|
|
|
return TRUE;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return FALSE;
|
|
|
|
}
|
|
|
|
|
2003-10-10 16:57:21 +02:00
|
|
|
void
|
|
|
|
sp_pcontext::push_cursor(LEX_STRING *name)
|
|
|
|
{
|
|
|
|
LEX_STRING n;
|
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
if (m_cursors.elements == m_max_cursor_index)
|
|
|
|
m_max_cursor_index+= 1;
|
2003-10-10 16:57:21 +02:00
|
|
|
n.str= name->str;
|
|
|
|
n.length= name->length;
|
2006-04-07 16:53:15 +02:00
|
|
|
insert_dynamic(&m_cursors, (gptr)&n);
|
2003-10-10 16:57:21 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
2006-04-07 16:53:15 +02:00
|
|
|
See comment for find_variable() above
|
|
|
|
*/
|
2003-10-10 16:57:21 +02:00
|
|
|
my_bool
|
2003-11-13 19:34:56 +01:00
|
|
|
sp_pcontext::find_cursor(LEX_STRING *name, uint *poff, my_bool scoped)
|
2003-10-10 16:57:21 +02:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
uint i= m_cursors.elements;
|
2003-11-13 19:34:56 +01:00
|
|
|
|
2004-08-26 12:54:30 +02:00
|
|
|
while (i--)
|
2003-10-10 16:57:21 +02:00
|
|
|
{
|
|
|
|
LEX_STRING n;
|
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
get_dynamic(&m_cursors, (gptr)&n, i);
|
2003-10-10 16:57:21 +02:00
|
|
|
if (my_strnncoll(system_charset_info,
|
|
|
|
(const uchar *)name->str, name->length,
|
|
|
|
(const uchar *)n.str, n.length) == 0)
|
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
*poff= m_cursor_offset + i;
|
2003-10-10 16:57:21 +02:00
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
}
|
2004-08-26 12:54:30 +02:00
|
|
|
if (!scoped && m_parent)
|
|
|
|
return m_parent->find_cursor(name, poff, scoped);
|
2003-10-10 16:57:21 +02:00
|
|
|
return FALSE;
|
|
|
|
}
|
2005-11-17 11:11:48 +01:00
|
|
|
|
2005-12-07 15:01:17 +01:00
|
|
|
|
|
|
|
void
|
|
|
|
sp_pcontext::retrieve_field_definitions(List<create_field> *field_def_lst)
|
|
|
|
{
|
|
|
|
/* Put local/context fields in the result list. */
|
|
|
|
|
2006-04-07 16:53:15 +02:00
|
|
|
for (uint i = 0; i < m_vars.elements; ++i)
|
2005-12-07 15:01:17 +01:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
sp_variable_t *var_def;
|
|
|
|
get_dynamic(&m_vars, (gptr) &var_def, i);
|
2005-12-07 15:01:17 +01:00
|
|
|
|
|
|
|
field_def_lst->push_back(&var_def->field_def);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Put the fields of the enclosed contexts in the result list. */
|
|
|
|
|
|
|
|
List_iterator_fast<sp_pcontext> li(m_children);
|
|
|
|
sp_pcontext *ctx;
|
|
|
|
|
|
|
|
while ((ctx = li++))
|
|
|
|
ctx->retrieve_field_definitions(field_def_lst);
|
|
|
|
}
|
|
|
|
|
2005-11-17 11:11:48 +01:00
|
|
|
/*
|
|
|
|
Find a cursor by offset from the top.
|
|
|
|
This is only used for debugging.
|
2006-04-07 16:53:15 +02:00
|
|
|
*/
|
2005-11-17 11:11:48 +01:00
|
|
|
my_bool
|
2005-11-18 16:30:27 +01:00
|
|
|
sp_pcontext::find_cursor(uint offset, LEX_STRING *n)
|
2005-11-17 11:11:48 +01:00
|
|
|
{
|
2006-04-07 16:53:15 +02:00
|
|
|
if (m_cursor_offset <= offset &&
|
|
|
|
offset < m_cursor_offset + m_cursors.elements)
|
2005-11-17 11:11:48 +01:00
|
|
|
{ // This frame
|
2006-04-07 16:53:15 +02:00
|
|
|
get_dynamic(&m_cursors, (gptr)n, offset - m_cursor_offset);
|
2005-11-17 11:11:48 +01:00
|
|
|
return TRUE;
|
|
|
|
}
|
2005-11-18 16:30:27 +01:00
|
|
|
if (m_parent)
|
|
|
|
return m_parent->find_cursor(offset, n); // Some previous frame
|
|
|
|
return FALSE; // index out of bounds
|
2005-11-17 11:11:48 +01:00
|
|
|
}
|