mirror of
https://github.com/MariaDB/server.git
synced 2025-09-29 12:29:12 +02:00
MariaDB server is a community developed fork of MySQL server. Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry.
amazon-web-servicesdatabasefulltext-searchgalerageographical-information-systeminnodbjsonmariadbmysqlrdbmsrelational-databasessqlstorage-enginevector-database
d8fc19495c
This change adds CURSOR declarations inside PACKAGE BODY.
PL/SQL mode:
SET sql_mode=ORACLE;
CREATE PACKAGE BODY pkg AS
CURSOR mc0 IS SELECT c0, c1 FROM t1;
PROCEDURE p1 AS
rec mc0%ROWTYPE;
BEGIN
OPEN mc0;
FETCH mc0 INTO rec;
CLOSE mc0
END;
END;
/
SQL/PSM mode:
SET sql_mode=DEFAULT;
CREATE PACKAGE BODY pkg
mc0 CURSOR FOR SELECT c0, c1 FROM t1;
PROCEDURE p1()
BEGIN
DECLARE rec ROW TYPE OF mc0;
OPEN mc0;
FETCH mc0 INTO rec;
CLOSE mc0
END;
END;
/
PACKAGE BODY cursors like local cursors
(declared inside a FUNCTION or a PROCEDURE) support:
- OPEN/FETCH/CLOSE
- FOR rec IN cur - an explicit cursor loop
- Using a cursor row as an anchored variable data type:
* DECLARE var cur%ROWTYPE; -- sql_mode=ORACLE
* DECLARE var ROW TYPE OF cur; -- sql_mode=DEFAULT
The patch details:
- Changing various class members and function/method parameters which
store a CURSOR run-time address from "uint" to sp_rcontext_addr.
A few classes now derive from sp_rcontext_addr instead of having
a "uint m_cursor;" member.
This change uses the same idea with what we did for SP variables,
when we implemented PACKAGE BODY variables a few years ago.
- Fixing the grammar in sql_yacc.yy to allow CURSOR declarations
inside PACKAGE BODY.
- Adding a new class sp_pcontext_top. It's used for the top level parse
context (of an sp_head). Note, its children contexts still use the old
class sp_pcontext.
sp_pcontext_top context additionally to sp_pcontext has:
const sp_head *m_sp; -- The pointer to the sp_head owning this context
Dynamic_array<sp_pcursor> m_member_cursors; -- PACKAGE BODY wide cursors
m_sp->m_parent->get_parse_context() is used to find the sp_pcontext
belonging to the parent PACKAGE BODY from a sp_pcontext_top instance
belonging to a PROCEDURE/FUNCTION sp_pcontext_top.
- Adding a new member in sp_rcontext:
Dynamic_array<sp_cursor*> m_member_cursors;
It's used to store run-time data of PACKAGE BODY wide cursors.
- Adding a new class sp_instr_copen2. It's used to open PACKAGE BODY cursors.
Unlike the usual cursors, PACKAGE BODY cursors:
* do not use the cursor stack (sp_rcontext::m_cstack)
* do not need a preceeding sp_instr_cpush
* do not need a following sp_instr_cpop
All cursor information such as "sp_lex_cursor" resides inside
sp_instr_copen2 itself (rather than inside sp_instr_cpush which is
used to store "sp_lex_cursor" in case of sp_instr_copen).
Note, the other cursor related instructions:
sp_instr_cfetch
sp_instr_cclose
sp_instr_cursor_copy_struct
do not need sp_instr_xxx2 counter-parts.
Thy just use sp_rcontext_addr to address cursors.
- Adding Sp_rcontext_handler_member
It's used to handle PACKAGE BODY members:
cursors and variables declared in the PACKAGE BODY,
when they are accessed from its executable initialization section:
CREATE PACKAGE BODY pkg AS
CURSOR mc0 IS SELECT c0, c1 FROM t1; -- A member (PACKAGE BODY cursor)
mv0 mc0%ROWTYPE; -- A member (PACKAGE BODY variable)
PROCEDURE p1 AS
BEGIN
-- Accessing members from here use sp_rcontext_handler_package_body
-- (members of the parent PACKAGE BODY)
OPEN mc0;
FETCH mc0 INTO mv0;
CLOSE mc0;
END;
BEGIN
-- NEW:
-- Accessing members from here use sp_rcontext_handler_member
-- (PACKAGE BODY own members)
OPEN mc0;
FETCH mc0 INTO mv0;
CLOSE mc0;
END;
/
Member variables and cursor are now marked with the "MEMBER." prefix
in the "SHOW PACKAGE BODY code" output.
Some old MTR tests have been re-recorded accordingly.
- Adding new virtual methods into Sp_rcontext_handler:
virtual const sp_variable *get_pvariable(const sp_pcontext *pctx,
uint offset) const;
virtual const sp_pcursor *get_pcursor(const sp_pcontext *pctx,
uint offset) const;
They're used from sp_instr::print() virtual implementations.
They internally calculate a proper sp_pcontext using as a parameter
the sp_pcontext pointed by sp_instr::m_ctx.
For example, Sp_handler_package_body::get_pvariable()/get_pcursor()
accesses to this sp_pcontext:
m_ctx->top_context()->m_sp->m_parent->get_parse_context(),
i.e. the parse context of the PACKAGE BODY which is the parent for
the current package PROCEDURE of FUNCTION an sp_instr belongs to.
- Adding a new method LEX::find_cursor(). It searches for a cursor in
this order:
1. Local cursors in the nearst surrounding BEGIN/END block.
2a. A member cursor of the current PACKAGE BODY
(used from the PACKAGE BODY initialization section)
OR
2b. A member cursor of the parrent PACKAGE BODY
(used from a package PROCEDURE or a package FUNCTION)
Adding a new method LEX::find_cursor_with_error().
In case when a cursor is not found, it automatically
raises the ER_SP_CURSOR_MISMATCH SQL condition into
the diagnostics area.
- Adding a new method sp_head::add_instr_copenX().
It creates sp_instr_copen for local cursors,
or sp_instr_copen2 for non-local cursors.
- Adding a new abstract class sp_lex_cursor_instr.
It's used a common parent class for a few sp_instr_xxx classes,
including the new sp_instr_copen2.
This change is needed to avoid code duplication.
- Adding a new protected method sp_instr::print_cmd_and_var(), to print
an instruction using this format: "command name@offset".
It's used from a few implementations of sp_instr_xxx::print(),
including sp_instr_copen2::print().
This change is also needed to avoid code duplication.
- Adding a new method sp_pcontext::frame_for_members_candidate(),
to distinguish easier between local cursors/variables and
PACKAGE BODY cursors/variables.
- Fixing "struct Lex_for_loop_st" to addionally store
a const pointer to Sp_rcontext_handler, to distinguish between:
* FOR rec IN local_cursor
* FOR rec IN package_body_cursor
|
||
|---|---|---|
| .github | ||
| BUILD | ||
| client | ||
| cmake | ||
| dbug | ||
| debian | ||
| Docs | ||
| extra | ||
| include | ||
| libmariadb@b5a2c9f3c2 | ||
| libmysqld | ||
| libservices | ||
| man | ||
| mysql-test | ||
| mysys | ||
| mysys_ssl | ||
| plugin | ||
| randgen/conf | ||
| scripts | ||
| sql | ||
| sql-bench | ||
| sql-common | ||
| storage | ||
| strings | ||
| support-files | ||
| tests | ||
| tpool | ||
| unittest | ||
| vio | ||
| win | ||
| wsrep-lib@e55f01ce1e | ||
| zlib | ||
| .clang-format | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| appveyor.yml | ||
| BUILD-CMAKE | ||
| CMakeLists.txt | ||
| CODING_STANDARDS.md | ||
| config.h.cmake | ||
| configure.cmake | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| CREDITS | ||
| INSTALL-SOURCE | ||
| INSTALL-WIN-SOURCE | ||
| KNOWN_BUGS.txt | ||
| README.md | ||
| SECURITY.md | ||
| THIRDPARTY | ||
| VERSION | ||
Code status:
ci.appveyor.com
MariaDB: The innovative open source database
MariaDB was designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.
MariaDB is brought to you by the MariaDB Foundation and the MariaDB Corporation. Please read the CREDITS file for details about the MariaDB Foundation, and who is developing MariaDB.
MariaDB is developed by many of the original developers of MySQL who now work for the MariaDB Corporation, the MariaDB Foundation and by many people in the community.
MySQL, which is the base of MariaDB, is a product and trademark of Oracle Corporation, Inc. For a list of developers and other contributors, see the Credits appendix. You can also run 'SHOW authors' to get a list of active contributors.
A description of the MariaDB project and a manual can be found at:
https://mariadb.com/kb/en/mariadb-vs-mysql-features/
https://mariadb.com/kb/en/mariadb-versus-mysql-compatibility/
https://mariadb.com/kb/en/new-and-old-releases/
Getting the code, building it and testing it
Refer to the following guide: https://mariadb.org/get-involved/getting-started-for-developers/get-code-build-test/ which outlines how to build the source code correctly and run the MariaDB testing framework, as well as which branch to target for your contributions.
Help
More help is available from the Maria Discuss mailing list https://lists.mariadb.org/postorius/lists/discuss.lists.mariadb.org/ and MariaDB's Zulip instance, https://mariadb.zulipchat.com/
Licensing
MariaDB is specifically available only under version 2 of the GNU General Public License (GPLv2). (I.e. Without the "any later version" clause.) This is inherited from MySQL. Please see the README file in the MySQL distribution for more information.
License information can be found in the COPYING file. Third party license information can be found in the THIRDPARTY file.
Bug Reports
Bug and/or error reports regarding MariaDB should be submitted at: https://jira.mariadb.org
For reporting security vulnerabilities, see our security-policy.
The code for MariaDB, including all revision history, can be found at: https://github.com/MariaDB/server