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

💡 [Feature Request] - Iterative (and consistent) Patching #867

Open
Isaac-GC opened this issue Mar 11, 2024 · 0 comments
Open

💡 [Feature Request] - Iterative (and consistent) Patching #867

Isaac-GC opened this issue Mar 11, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Isaac-GC
Copy link
Collaborator

Summary

The database will be checked to see if a patch has been applied, and if not, applies the patch regardless of the version.

What problem are you trying to solve?

As patching the database only applies to a single hardcoded value (i.e. v0.2). After the very next patch release, the first patch won't be applied, creating a non-linear and inconsistent database patching methodology.

For example: If patch A is released for v0.2, but the user upgrades directly to v0.3 from v0.1, bypassing v0.2, the patch won't properly be applied.

Basic Example

The database (either internally to the DB and/or via an embedded schema asset in the application) will contain a history of the applied patches as well current version of the database. By doing it this way, even if application versions are bypassed, the patches will still be incrementally/consistently applied, ensuring repeatable outputs.

Drawbacks

Patches will need to be retroactively ported to this new patching methodology and the whole system will be a medium to large-ish undertaking to ensure the system works as expected and won't impact users.

Reference Issues

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant