10643cffe9
Oracle mode has no priority between set-operators but the current implementation with disable_index_if_needed() can not work with arbitrary mix of distinct/non-distinct set-operators as the algorithm is tied to the properly wrapped version of expression. Index can be disabled only once and cannot be reenabled afterwards. To adapt Oracle mode for the aforementioned implementation we prioritize each set operator with parens in the order of appearance. So the expression: S1 op1 S2 op2 S3 op3 S4 will be rewritten like this: (((S1 op1 S2) op2 S3) op3 S4). The rewritten expression is valid for both Oracle and default mode and renders the same result. Prioritizing is done with create_priority_nest() but it was tweaked to work with derived to be the first operand. Originally create_priority_nest() could wrap only second operand, like this: S1 op1 S2 op2 S3 -> S1 op1 (S2 op2 S3). Now this behaviour is kept by non-NULL attach_to argument. With NULL attach_to argument it produces this transformation: S1 op1 S2 -> (S1 op1 S2), but to be strict it will look like this: SELECT .. FROM (S1 op1 S2). This expression is treated as the first one in the select list, so nothing to "attach to". On importance of not making fake_select_lex after create_priority_nest() in parsed_select_expr_start(). This will fail nastily in Protocol::valid_handler() check in store_longlong() for EXPLAIN. This happens because select_options are inherited from newly made fake_select_lex but without SELECT_DESCRIBE flag which is meant to be assigned by mysql_explain_union() but union_needs_tmp_table() is false (because now top-level unit has no set-operator, it is just select from derived), so SELECT_DESCRIBE assignment is skipped. Depending on that flag send_result_set_metadata() is conditionally executed in JOIN::exec_inner(). And originally it is done via select_describe() branch for top-level select when there is no set operator (it is select from derived as explained above), not via direct send_result_set_metadata(). On IS_OR_WAS_ORACLE. Sql_mode_save_for_frm_handling removes MODE_ORACLE when view is registered or opened. We cannot return it back as this conflicts with MDEV-12478 (tested by compat/oracle.func_concat). So we are temporarily adding WAS_ORACLE flag instead. WAS_MODE_ORACLE is for testing both WAS_ORACLE and MODE_ORACLE simultaneously. |
||
|---|---|---|
| .github | ||
| BUILD | ||
| client | ||
| cmake | ||
| dbug | ||
| debian | ||
| Docs | ||
| extra | ||
| include | ||
| libmariadb@9e2b0370de | ||
| 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@7010f0ab58 | ||
| zlib | ||
| .clang-format | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| appveyor.yml | ||
| BUILD-CMAKE | ||
| CMakeLists.txt | ||
| config.h.cmake | ||
| configure.cmake | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| CREDITS | ||
| INSTALL-SOURCE | ||
| INSTALL-WIN-SOURCE | ||
| KNOWN_BUGS.txt | ||
| README.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: https://mariadb.org/about/security-policy/
The code for MariaDB, including all revision history, can be found at: https://github.com/MariaDB/server