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
CockroachDB 2.0 support #1970
Comments
As stated in the docs, current support is for 1.1 only. |
I'm having the same issues with the 2.0 version. Line 45 in 2e60430
But it seems that CockroachDB 2.0 doesn't create a record for the user databases in the pg_namespace table. This can be fixed if we use pg_database instead of pg_namespace. |
I was digging into the CockroachDB and it seems that they do not support "custom" schemas inside the databases, the 'public' schema is always fixed to the user objects. |
I don't need custom schemas. Making flyway work only with |
Hello @axelfontaine , Is there any "CI" builds we can use as a temporary solution while the next release is out? |
This should be resolved in Flyway 5.1 cc @axelfontaine |
@cristhiank We expect this to land on master early next week. From then on you will be able to build Flyway from source to use it until the official 5.1 release. |
We have just pushed support for CockroachDB 2.0. The current master now supports both CockroachDB 1.1 and 2.0. There are no known issues. You can access it by building from source until the official 5.1 release. |
@axelfontaine could you tell us when flyway version 5.1 will be released. |
I'm also waiting 5.1 because I don't know how to compile it and don't want to waste time learning it. |
You can use this temporarily, basically pulls from the master branch https://plugins.gradle.org/plugin/com.radioafricagroup.plugins.flyway. Also make sure to include jitpack.io in your build script repositories. Also I documented this here. |
Thank you for the release! |
https://github.com/cockroachdb/cockroach/releases
I tried to execute
flyway clean
andflyway baseline
but I kept getting errors about scheme. All attempts to fix it by changing config parameters have failed.I just want to know if it's officially supported.
The text was updated successfully, but these errors were encountered: