I would like to use Flyway for schema migration management, but have hit an issue using it with Cockroach. If I have the jdbc url connect to the defaulted, and have the managed schema listed under flyway.schema, when performing a baseline (or migrate), Flyway will check for the existence of the database, create it if it does not exist, and then create and populate its schema versioning table.
Using the above configuration setup, whereby Flyway would need to create the database (in a new deployment for example), the transaction hangs indefinitely. Now, if I change the config so I must assume that the managed database already exists, and have it contained in the jdbc url, then Flyway can create the versioning table and the rest of the managed schema tables just fine.
I’m testing this on version 2.1, and have also tried on version 19.1.
I noticed some previous bugs in GitHub (e.g. https://github.com/cockroachdb/cockroach/issues/39667), however these have been closed.
Is this still a bug? If not should I raise a bug on GitHub?