MDEV-39222: Error when inserting data from seq#4897
Open
bsrikanth-mariadb wants to merge 1 commit intobb-12.3-MDEV-38805-dev-sprint-work-2from
Open
MDEV-39222: Error when inserting data from seq#4897bsrikanth-mariadb wants to merge 1 commit intobb-12.3-MDEV-38805-dev-sprint-work-2from
bsrikanth-mariadb wants to merge 1 commit intobb-12.3-MDEV-38805-dev-sprint-work-2from
Conversation
When the replayed optimizer context doesn't contain seq table info, which is used to insert data into a new/existing table, errors are displayed. This is happening because, if any table or index that is used by the engine is not available in the context, then a warning is generated. However, this warning is converted to an error message for insert into statements. Solution here is not to continue using the replayed context after the required query has been replayed.
bsrikanth-mariadb
force-pushed
the
12.3-MDEV-39222-error-with-insert-into-from-seq
branch
from
57a172f to
9692a89
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the replayed optimizer context doesn't contain seq table info, which is used to insert data into a new/existing table, errors are displayed. This is happening because, if any table or index that is used by the engine is not available in the context, then a warning is generated. However, this warning is converted to an error message for insert into statements.
Solution here is not to continue using the replayed context after the required query has been replayed.