-
Notifications
You must be signed in to change notification settings - Fork 86
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 script that prints clickhouse auto migration diff #3474
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
f535ca3
to
1f10219
Compare
9d01b29
to
42936c2
Compare
4185055
to
d97dadb
Compare
42936c2
to
a587d1a
Compare
d97dadb
to
2f95ef1
Compare
2f95ef1
to
b5dd71f
Compare
b5dd71f
to
1893e17
Compare
bd2cefb
to
b5e3e5e
Compare
b5e3e5e
to
f7fa0a9
Compare
9034304
to
933085e
Compare
933085e
to
2c3af4d
Compare
I realized I could simplify this script by fixing something in the gorm clickhouse driver. It's taking some time to get that change approved, so I added a local buildpatch in this PR. @luluz66 could you please take another look at this? My PR to gorm-clickhouse with more context on the problem: go-gorm/clickhouse#91 As a reminder, currently clickhouse gorm autoMigrate always runs column migrations, even if there aren't any schema changes (the reason for that is describe in the PR above). In addition to being unnecessary, it also makes this schema change script less useful, because it appears as if we're always running a migration, and makes it harder to detect when we're making a meaningful schema change. Applying this patch will fix both of those problems |
Fixes buildbuddy-io/buildbuddy-internal#2096 |
Fixes buildbuddy-io/buildbuddy-internal#2096