1berry/MariaDB-server
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Typo Errors Fixed like essensially->essentially

Browse Source
This commit is contained in:
Rajat Rawat 2017-12-25 23:11:56 +05:30 committed by Sergey Vojtovich
parent 8307fc9d6c
commit 7a66e0ab8f
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Docs/sp-imp-spec.txt
View File

@ -103,7 +103,7 @@
- Statements: - Statements:
The Lex in THD is replaced by a new Lex structure and the statement, The Lex in THD is replaced by a new Lex structure and the statement,
is parsed as usual. A sp_instr_stmt is created, containing the new is parsed as usual. A sp_instr_stmt is created, containing the new
Lex, and added to added to the instructions in sphead. Lex, and added to the instructions in sphead.
Afterwards, the procedure's Lex is restored in THD. Afterwards, the procedure's Lex is restored in THD.
- SET var: - SET var:
Setting a local variable generates a sp_instr_set instruction, Setting a local variable generates a sp_instr_set instruction,
@ -169,7 +169,7 @@
- Parsing CREATE FUNCTION ... - Parsing CREATE FUNCTION ...
Creating a functions is essensially the same thing as for a PROCEDURE, Creating a functions is essentially the same thing as for a PROCEDURE,
with the addition that a FUNCTION has a return type and a RETURN with the addition that a FUNCTION has a return type and a RETURN
statement, but no OUT or INOUT parameters. statement, but no OUT or INOUT parameters.
@ -189,7 +189,7 @@
additional requirement. They will be called in expressions with the same additional requirement. They will be called in expressions with the same
syntax as UDFs, so UDFs and stored FUNCTIONs share the namespace. Thus, syntax as UDFs, so UDFs and stored FUNCTIONs share the namespace. Thus,
we must make sure that we do not have UDFs and FUNCTIONs with the same we must make sure that we do not have UDFs and FUNCTIONs with the same
name (even if they are storded in different places). name (even if they are stored in different places).
This means that we can reparse the procedure as many time as we want. This means that we can reparse the procedure as many time as we want.
The first time, the resulting Lex is used to store the procedure in The first time, the resulting Lex is used to store the procedure in
@ -225,7 +225,7 @@
sql_parse.cc:mysql_execute_command() then uses sp.cc:sp_find() to sql_parse.cc:mysql_execute_command() then uses sp.cc:sp_find() to
get the sp_head for the procedure (which may have been read from the get the sp_head for the procedure (which may have been read from the
database or feetched from the in-memory cache) and calls the sp_head's database or fetched from the in-memory cache) and calls the sp_head's
method execute(). method execute().
Note: It's important that substatements called by the procedure do not Note: It's important that substatements called by the procedure do not
do send_ok(). Fortunately, there is a flag in THD->net to disable do send_ok(). Fortunately, there is a flag in THD->net to disable
@ -545,7 +545,7 @@
Cons: Uses more memory, each SP read from table once per thread. Cons: Uses more memory, each SP read from table once per thread.
Unfortunately, we cannot use alternative 1 for the time being, as most Unfortunately, we cannot use alternative 1 for the time being, as most
of the datastructures to be cached (lex and items) are not reentrant of the data structures to be cached (lex and items) are not reentrant
and thread-safe. (Things are modifed at execution, we have THD pointers and thread-safe. (Things are modifed at execution, we have THD pointers
stored everywhere, etc.) stored everywhere, etc.)
This leaves us with alternative 2, one cache per thread; or actually This leaves us with alternative 2, one cache per thread; or actually