Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use migrations to update database schema more easily #174

Open
utarwyn opened this issue Sep 30, 2021 · 0 comments
Open

Use migrations to update database schema more easily #174

utarwyn opened this issue Sep 30, 2021 · 0 comments
Assignees
Labels
type: enhancement Features and feature requests.
Milestone

Comments

@utarwyn
Copy link
Owner

utarwyn commented Sep 30, 2021

Is your feature request related to a problem? Please describe.
As the plugin will receive more and more features, the database schema is destined to change in future versions and especially v2.3.0. Currently the plugin only creates tables that do not yet exist in the database. BUT it will not be easy to migrate on new versions for servers owners who already have a lot of data.

Describe the solution you'd like
The main idea is to create a solution based on https://flywaydb.org with migration files that will be executed at the plugin start when current plugin version is more recent than the one already registered. To do so, we have to save plugin version somewhere (in the config file I think because it already stores that information).

# # # # # # # # # # # # # # # # # # # # #
# EnderContainers configuration #
# Version: 2.3.0-dev #
# An enderchests plugin by Utarwyn #
# # # # # # # # # # # # # # # # # # # # #

@utarwyn utarwyn added the type: enhancement Features and feature requests. label Sep 30, 2021
@utarwyn utarwyn added this to the v2.3.x milestone Sep 30, 2021
@utarwyn utarwyn self-assigned this Sep 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Features and feature requests.
Projects
None yet
Development

No branches or pull requests

1 participant