Remove schema.sql in favor of schema.php file #72
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
This only duplicates the maintance effort. It is recommended to either use the schema.php file or db migrations (CakeDC plugin).
|
I agree that adding Migration files would be a good step in the right direction. Since there are currently no changes planned for the db-schema of the plugin I'm not worried about any maintenance effort. If there are more/bigger changes planned in the future then I agree that this file can be removed |
|
@xhs345 keeping it seems to me like proposing an outdated practise. |
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.
This only duplicates the maintance effort.
It is recommended to either use the schema.php file or db migrations (CakeDC plugin).