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

Add check for backwards compatibility #406

Open
stanyq4 opened this issue Dec 1, 2021 · 0 comments
Open

Add check for backwards compatibility #406

stanyq4 opened this issue Dec 1, 2021 · 0 comments

Comments

@stanyq4
Copy link

stanyq4 commented Dec 1, 2021

In our development process, we enforce 100% backwards compatibility to all the DB schema changes to support all the legacy.
The process of enforcement is only done during the schema design phase and code review phase, which means there is still a potential for human error.

We are looking to add a programmatic check to accomplish backwards compatibility.

Something like:

  • Any change to a field structure (Data Type/Object Structure) should be performed by introducing a new field instead of mutating an existing one.

Before applying changes - analyze the existing data and ensure the change will not break rules.

This would be a new flag -ensureBackwardsCompatibility during the run phase.

Is this something you considered or are there alternative ways to achieve our goal?

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

No branches or pull requests

1 participant