-
Notifications
You must be signed in to change notification settings - Fork 60
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
[WIP] Schema evolution code generation #441
Conversation
Just for clarification from my side: This means we still keep 430 as it is and merge it separately, or we close that and keep this one for the feature? |
Since I am fixing bugs in #430, I think we better close it. I previously thought functionality in there was stable. |
Co-authored-by: Andre Sailer <[email protected]>
Rebased this onto #460. For me locally there are a few test issues with the datamodel storage roundtrip tests, because they now trip over the fact that for the schema evolution tests we generate "old" I don't have a real fix for that yet, but I would simply wait for now to see how the final solution to schema evolution looks like and then fix those tests afterwards. |
Since based on #430 , this development will not be integrated. |
BEGINRELEASENOTES
exactly as it appears between the two bold lines
ENDRELEASENOTES
Based on #430