Fix mysql migration script of 1.9.20 #309
Open
Conversation
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
2 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.
This PR is a rework of #272.
What happened
testlink_create_tablesandalter_tableswill be different.Intent of the change
Add unsigned
According to testlink_create_tables.sql, the
enable_on_designandenable_on_executioncolumns of the platforms table seem to expect unsigned.However, the SQL for the migration alter_table does not have unsigned, so when migrating from 1.9.20 or lower versions, there is a difference compared to the initial preparation of 1.9.20.
Assuming that
testlink_create_tables.sqlis the correct structure, this changes will be necessary.