-
Notifications
You must be signed in to change notification settings - Fork 17
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
Generated YAML changelogs do not contain necessary modifySql items #108
Comments
Likely related to #85 |
This is indeed the same issue as #85. Interleaved tables and column options are Spanner specific features that don't really fit that well into the model of Liquibase, as they cannot really be mapped directly to a generic SQL feature. (Column options might actually be a little easier than interleaved tables) |
I believe the expectation is that changelogs should be round-trippable. That is to say that if you have DB My concern is that the limitations of the current implementation would also mean that operations such as |
I'm trying to generate an initial YAML changelog from an existing Spanner database. I find that the generated YAML doesn't contain the necessary
modifySql
items for things likeINTERLEAVE IN PARENT
orOPTIONS (allow_commit_timestamp = true)
.The text was updated successfully, but these errors were encountered: