EZEE-3214: Dropped default value from Workflow Markings message column #149
Conversation
This file contains 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
lserwatka
approved these changes
Jul 2, 2020
adamwojs
approved these changes
Jul 2, 2020
|
Hi, thanks for the update @alongosz |
Hi @Omone. ALTER TABLE ezeditorialworkflow_markings
ADD COLUMN message TEXT NOT NULL default (''),the difference is in braces, which introduce expression-ish thing. |
mnocon
approved these changes
Jul 20, 2020
lserwatka
deleted the
base-3.0/ezee-3214-drop-wf-markings-message-col-default
branch
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
JIRA issue: EZEE-3214
Type: bug
We still seem to support MySQL 5.7. Unfortunately default values for TEXT columns are not supported in that version.
Seems like Workflow Gateway sets it by default so it's rather required. Current schema seems to confirm that as well.
Hence the change.