-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Fix for SYSTEM VERSIONED tables #14514, #14515, and #14516 #14536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Vincent Milum Jr <git@darkain.com>
Signed-off-by: Vincent Milum Jr <git@darkain.com>
…er params Signed-off-by: Vincent Milum Jr <git@darkain.com>
Signed-off-by: Vincent Milum Jr <git@darkain.com>
MauricioFauth
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution!
I don't know why Travis CI didn't run, but you also need to fix the failing tests.
Co-Authored-By: darkain <git@darkain.com>
Co-Authored-By: darkain <git@darkain.com>
Co-Authored-By: darkain <git@darkain.com>
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Merged, thanks for your contribution! |
Fixes #14514 Fixes #14515 Possible fix for #14516 #14514 Tables which enable the new MariaDB 10.3 versioning show up as "SYSTEM VERSIONED" instead of "BASE TABLE" inside of information schema. This patch now checks for both, so these new table types don't incorrectly display as views. #14515 MariaDB 10.3 also supports INVISIBLE columns, which is optionally paired with SYSTEM VERSIONED tabled (or implemented separately). This patch helps handle this new column attribute. #14516 This patch cannot be fully tested and verified with current MariaDB builds. Version 10.3.9 (currently unreleased) corrects an issue with column information for SYSTEM VERSIONED columns that this patch relies on. https://jira.mariadb.org/browse/MDEV-16804 - the reason for checking with preg_match instead of adding to the list is because there are now combined "extra" information for columns, such as INVISIBLE columns. Just matching entire strings also has a bug with these other "extra" parameters. Signed-off-by: Vincent Milum Jr <git@darkain.com> Signed-off-by: Maurício Meneghini Fauth <mauriciofauth@gmail.com> (cherry picked from commit 3f6e360) Signed-off-by: Maurício Meneghini Fauth <mauriciofauth@gmail.com>
Related to #14536 Signed-off-by: Maurício Meneghini Fauth <mauriciofauth@gmail.com>
Fixes #14514
Fixes #14515
Possible fix for #14516
#14514 Tables which enable the new MariaDB 10.3 versioning show up as "SYSTEM VERSIONED" instead of "BASE TABLE" inside of information schema. This patch now checks for both, so these new table types don't incorrectly display as views.
#14515 MariaDB 10.3 also supports INVISIBLE columns, which is optionally paired with SYSTEM VERSIONED tabled (or implemented separately). This patch helps handle this new column attribute.
#14516 This patch cannot be fully tested and verified with current MariaDB builds. Version 10.3.9 (currently unreleased) corrects an issue with column information for SYSTEM VERSIONED columns that this patch relies on. https://jira.mariadb.org/browse/MDEV-16804 - the reason for checking with preg_match instead of adding to the list is because there are now combined "extra" information for columns, such as INVISIBLE columns. Just matching entire strings also has a bug with these other "extra" parameters.
Before submitting pull request, please check that every commit: