You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running goose on a clickhouse cluster, it fails to get the list of "previous" migrations (sometime querying a node a get a partial list of migrations)
It could be possible to have it depend on an environment variable. To be able to support both replicated and non-replicated setups I do the following in my own migrations:
I'm curious, are folks using goose as a Go library or a standalone CLI tool?
I was thinking of setting up github.com/pressly/goose-dialects with community-supported dialects, which can include the various flavors of ClickHouse requests. Still need to think through whether this is a good idea or not, and whether it'll even work. But it's one option, and would at least satisfy the "goose as a provider in Go code".
When running goose on a clickhouse cluster, it fails to get the list of "previous" migrations (sometime querying a node a get a partial list of migrations)
Possible fix:
Not sure how this can be defined in goose via the CreateTable function (or should it be a new driver ? 🤔 )
The text was updated successfully, but these errors were encountered: