4de3d55db3
Allow limited ALTER TABLE on explicit system columns ROW START/ROW
END. That includes two CHANGE COLUMN (or MODIFY COLUMN) operations:
1. change INVISIBLE property;
2. rename system field.*
That required a number of reworks. Vers_parse_info::fix_alter_info()
now better detects errors. It takes into account whether system
versioning is implicit (system hidden row_start/row_end) or
explicit, and case of explicit it allows the above two operations.
For changing invisible property it was required to add it into
Alter_column and take from there in mysql_prepare_alter_table().
Also the number of semantics are made more clear:
- ALTER_VERS_IMPLICIT/ALTER_VERS_EXPLICIT flags represent
corresponding operations for implicit<->explicit switch;
- ALTER_VERS_CHANGE is (ALTER_ADD_SYSTEM_VERSIONING |
ALTER_VERS_EXPLICIT | ALTER_VERS_IMPLICIT), so it is whether we
add system versioning or switch implicit<->explicit. It is used to
determine whether parser data check is required (check_parser_data()).
- check_parser_data() is new better name for check_conditions(), it
better reflects what it does.
- There is clear distinction between parser data and processed
data. Now we do not change as_row property, but add new sys_fields
property instead. We do not change period property as well, so it
is clear if PERIOD was specified in command or not at any
stage. Same with as_row, as it is now sole representation of AS
ROW clauses.
- The main point of updating sys_fields is check_sys_fields(), but
it is not the only point as check_sys_fields() not always needed.
When creating FRM we take processed data from sys_fields, i.e. the
data passed validation stage of check_parser_data()/check_sys_fields().
* Note that before the patch RENAME COLUMN worked but CHANGE COLUMN
alternative syntax produced ER_VERS_DUPLICATE_ROW_START_END.
|
||
|---|---|---|
| .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