[no-release-notes] Add regression test for long trigger names#9660
Merged
[no-release-notes] Add regression test for long trigger names#9660
Conversation
…triggers for a trigger with a long name
|
This PR is being tested for SQL correctness. Please allow ~25 mins for this to complete. If this PR does not result in a SQL correctness regression, the |
Contributor
Contributor
|
@coffeegoddd DOLT
|
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
3 participants
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.
A customer reported an issue with a query that joined the
dolt_schemastable with theinformation_schema.triggerstable. Due to a trigger name exceeding the schema limit of 64 chars, the data wasn't able to be converted into a result. The fix for this issue is in dolthub/go-mysql-server#3152 and this PR adds an additional regression test to Dolt, with the exact customer query.