Fix missing comma in entry_vendor_task index definition#13966
Open
mehmetozzen wants to merge 1 commit into
Open
Fix missing comma in entry_vendor_task index definition#13966mehmetozzen wants to merge 1 commit into
mehmetozzen wants to merge 1 commit into
Conversation
CREATE TABLE fails with a syntax error on MySQL 5.7 fresh installs due to a missing comma after the reach_profile_queue_time index definition.
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
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.
CREATE TABLE fails with a syntax error on MySQL 5.7 fresh installs due to
a missing comma after the reach_profile_queue_time index definition.
Pull Request Checklist
Please complete the following before submitting:
General notes -
New Kaltura Types
New Kaltura Services / Actions
Questions
What is the purpose of this PR?
entry_vendor_tasktable DDL where a missing comma between index definitions caused fresh installation scripts to fail.Does this change affect production code or infrastructure?
If yes, what is the rollback plan?