`migrate` CLI reports `error: no scheme` despite having supplied connection string.

[golang-migrate]

`migrate` CLI reports `error: no scheme` despite having supplied connection string.

[mingp]

@dhui

Thank you for the information. I tried your suggestion, and it worked.

For future reference, in case anyone else comes across this with the same issue, the command I used was as follows.

migrate -database "postgres://redacted:[email protected]:5432/redacted?sslmode=disable" -path "./migrations/" up 1 

[pavel-kalmykov]

Anyway it could be an improvement to have more specific messages about what is missing in order to make a migration

[glebarez]

Anyway it could be an improvement to have more specific messages about what is missing in order to make a migration

agreed, terrible error strings for such a popular product, I will take my start back

[pavel-kalmykov]

I got this error solved by providing the -path argument pointing to the directory where all the SQL scripts were stored

[mingp]

@paveltrufi

Thank you for the quick response.

I tried your suggestion, to include a -path argument. The command I am now running is as follows. This no longer encounters the error: no scheme error.

migrate -database postgres://redacted:[email protected]:5432/redacted -path ./migrations up 1

In retrospect, that error message was confusing. I will try to look deeper into why it reports that error message for a different underlying error.

Actually, I am still encountering an error, albeit a different one now. The error message is as follows, included here just for completeness. Although, this time, I'm inclined to believe the error message is legitimate, and the underlying issue is that the default Postgres install using Homebrew has no SSL certificate.

error: pq: SSL is not enabled on the server

I am closing this, as I believe it to be resolved. Thank you again for your help.

[dhui]

@mingp
If you install the migrate CLI via the Go toolchain, the version will be "dev". This is because versions are managed using git tags. See: our Makefile
We could start tracking version numbers in the code as well, but that allows for inconsistencies.

If you want the migrate binary to report the correct SemVer, you'll need to download the binaries from the release page or from package cloud

For the ssl issue, try specifying sslmode=disable in your connection string. For more info about the connection string, checkout the pq docs

[arkhamvm]

Just spend over 2 hours with this error, it MUST be more specific

[praneetloke]

In my case, it was because I was accidentally encoding the entire DB URL instead of just the password as per https://github.com/golang-migrate/migrate#database-urls. 🤦‍♂️